Steffen ProhaskaThere are discussions on the mailing list that git-cvsimport fails to handle history. This should be noted in the documentation of cvsimport.
Signed-off-by: Steffen Prohaska <prohaska@zib.de> --- Documentation/git-cvsimport.txt | 10 ++++++++++ 1 files changed, 10 insertions(+), 0 deletions(-)
Show changes to Documentation/git-cvsimport.txt +10 −0
diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt index fdd7ec7..b4a5ebd 100644 --- a/Documentation/git-cvsimport.txt +++ b/Documentation/git-cvsimport.txt @@ -31,6 +31,16 @@ to work with; after that, you need to 'git merge' incremental imports, or any CVS branches, yourself. It is advisable to specify a named remote via -r to separate and protect the incoming branches. +There were rumors on the mailing list that git-cvsimport fails to +handle history correctly. Especially cvs branches seem to cause +problems. See the following thread on the mailing list for more details +link:http://marc.info/?t=118385570200002&r=1&w=2[http://marc.info/?t=118385570200002&r=1&w=2]. +Alternatives discussed on the mailing list are + + * parsecvs from link:http://anongit.freedesktop.org/git/users/keithp/repos/parsecvs.git/[http://anongit.freedesktop.org/git/users/keithp/repos/parsecvs.git/] + * fromcvs from link:http://ww2.fs.ei.tum.de/%7Ecorecode/hg/fromcvs/[http://ww2.fs.ei.tum.de/%7Ecorecode/hg/fromcvs/] + +As of July 2007 there is no definite recommendation which tool to use. OPTIONS -------
-- 1.5.3.rc0.22.gd22ed