On 6/20/06, Jon Smirl <jonsmirl@xxxxxxxxx> wrote:
The plan is to modify rcs2git from parsecvs to create all of the git objects for the tree.
Sounds like a good plan. Have you seen recent discussions about it being impossible to repack usefully when you don't have trees (and resulting performance problems on ext3).
cvs2svn seems to do a good job at generating the trees.
No doubt. Gut the last stage, and use all the data in the intermediate DBs to run a git import. It's a great plan, and if you can understand that Python code... all yours ;-)
exactly sure how the changeset detection algorithms in the three apps compare, but cvs2svn is not having any trouble building changesets for Mozilla. The other two apps have some issues, cvsps throws away some of the branches and parsecvs can't complete the analysis.
Have you tried a recent parsecvs from Keith's tree? There's been quite a bit of activity there too. And Keith's interested in sorting out incremental imports too, which you need for a reasonable Moz transition plan as well. cheers, martin - : 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