# 
# patch "monotone.texi"
#  from [fe567b00feece4207218ba6314e1122a5d083882]
#    to [1aeed06f449777514c37695ac96ec281a63f6bc9]
# 
========================================================================
--- monotone.texi	fe567b00feece4207218ba6314e1122a5d083882
+++ monotone.texi	1aeed06f449777514c37695ac96ec281a63f6bc9
@@ -3117,11 +3117,56 @@
 If you merged two branches, monotone will gather all changelogs unknown to
 the server and attach it to the merge.
 
-FIXME: write about --direction flag
-
 If you change into your working directory you can omit specifying the branch
 as usual.
 
+Design Goals
+
address@hidden
address@hidden
+Cvssync (as this feature is called) should be nearly as bandwith efficient
+as this functionality can get (at least it should never be more expansive
+than using CVS itself).
address@hidden
+Synchronizing between multiple CVS servers for the same project should be
+possible (though this might get confusing and inconvenient).
address@hidden itemize
+
+Shortcomings
+
address@hidden
address@hidden
address@hidden is not yet implemented.
address@hidden
+missing side branch support (@code{--cvsbranch})
address@hidden
+creating new subdirectories on the CVS server is unimplemented
address@hidden
+a patch (MD5) failure is not handled gracefully
address@hidden
+full history import stresses the server (CVS' fault)
address@hidden
+not designed with memory efficiency in mind (like the cvs import feature)
address@hidden
+relies on checkin time to reconstruct the graph instead of RCS revisions
address@hidden
+no project creation on a CVS server (initial import)
address@hidden itemize
+
+Advanced Use:
+
address@hidden
address@hidden
+Working with CVS branches. @code{--cvsbranch}? (not yet implemented)
address@hidden
+Specifying a @code{--direction} when a fork occurs during cvs_push. (not yet 
+implemented)
address@hidden itemize
+
+Future directions:
+
+Perhaps multiple repository pull (mass update) in one command.
+
 @page
 @node    CVS Phrasebook
 @chapter CVS Phrasebook