Documentation: reorganize cvs-migration.txt
commitcd976f5c52694acb4b23c3f2425ed4f0a47ec799
authorJ. Bruce Fields <bfields@fieldses.org>
Thu, 7 Dec 2006 04:18:05 +0000 (6 23:18 -0500)
committerJunio C Hamano <junkio@cox.net>
Thu, 7 Dec 2006 05:35:53 +0000 (6 21:35 -0800)
tree22a28f1c50542e1bce82453ec06ec9e6d4e5431b
parentde51faf3888505fa3d661d4c35f32ecaf9fa1087
Documentation: reorganize cvs-migration.txt

Modify cvs-migration.txt so it explains first how to develop against a
shared repository, then how to set up a shared repository, then how to
import a repository from cvs.  Though this seems chronologically
backwards, it's still readable in this order, and it puts the more
commonly needed material closer to the front.

Remove the annotate/pickaxe section; perhaps it can find a place elsewhere
in the future.  Remove most of the "why git is better than cvs" stuff from
the introduction.

Add some minor clarifications, including two that have come up several
times on the mailing list:

1. Recommend committing any changes before running pull.
2. Note that changes must be commited before they can be pushed.

Update the clone discussion to reflect the new --use-separate-remotes
default, and add a brief mention of git-cvsserver.

Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/cvs-migration.txt