Converting from CVS would be a lot more efficient if all of revisions contained in a CVS file were written into git at the same time. So, if I extract complete revisions from 100 source files into git objects and then ask git to incremental pack, will git find all of the deltas and do a good job packing? Some of these files have thousands (50MB) of deltas. Also, note that I have not written any tree info into git yet. After all of the revisions are into git, I will follow up with the tree info and then repack all. How will the pack end up grouped, chronologically or will it still be sorted by file? It is not clear to me how the tree info interacts with the magic packing sauce. The plan is to modify rcs2git from parsecvs to create all of the git objects for the tree. It would be called by the cvs2svn code which would track the object IDs through the changeset generation process. At the end it will write all of the trees connecting the objects together. cvs2svn seems to do a good job at generating the trees. I am not 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. -- Jon Smirl jonsmirl@xxxxxxxxx - : 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