Hi Jon, On Mon, 31 Jul 2006, Jon Smirl wrote: > On 7/31/06, Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote: > > > would be to use cvs2svn to build the changeset database and then use > > > cvsps to simply read the changesets out of it and build the git > > > repository. > > > > Once cvs2svn has the db built, it should be easy to write a > > perl/python script that mimics the output of cvsps. > > This is an efficiency problem. In another mail, you asked for a solution for the initial 700MB download. How about doing it like Linux-2.6, namely have a clean cut, and for those who want, they can load the historical repo, too, and graft it onto the current one? I _think_ that with a new start, incremental git-cvsimport should still work, if you do it cleverly. Obviously, it would _not_ have the full history, but rather add onto the most recent revisions (incremental git-cvsimport detects the revisions to import by author date IIRC). Note that this method will _not_ work, if there are _new_ branches that cvsps has problems with. Ciao, Dscho - : 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