Martin Langhoff wrote: ... > Yes, cvsps is relying on the wrong things. I am looking at parsecvs > and the cvs2svn tool and wondering where to from here. ... > I am starting to look at what I can do with cvs2svn to get the import > into git. It seems to get very good patchsets, and it yields an easily > readable DB. I'll either learn Python, or read the DB from Perl > (probably from git-cvsimport). SVN has a portable format called "dumpfile" (see http://svn.collab.net/repos/svn/trunk/notes/fs_dumprestore.txt) which is produced by "svnadmin dump ..." and "cvs2svn --dump-only ...". Why not use it as input for importing into git? Pros: - "svnadmin dump" should be fast - svn repositories can be tracked with "svnadmin dump" (just remember the last imported revision and restart from there) - cvs2svn seems to be very good at its job - only one tool needed Cons: - Both svnadmin and cvs2svn only work on local repositories - cvs2svn cannot be used for tracking Regards Stephan - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html