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. My strategy instead is to build the git objects for the revisions when the CVS file is initially parsed and then track the sha-1 of the object. Otherwise I end up needing to use CVS to pull each revision out after the changeseta are computed and that's a slow process since it involves 1M forks of a cvs process. People on the Python list have been giving me some pointers on how to build the revision files efficiently. That's what I am working on right now. -- 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