On 8/1/06, Jon Smirl <jonsmirl@xxxxxxxxx> 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. My strategy instead is to build the git
Agreed when it comes to the initial import. I thought you were meaning for "driving" git-cvsimport when doing incrementals.
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.
You can definitely steal that from parsecvs -- it should be trivial to get parsecvs to do the RCS -> GIT part and store on disk the path/revision -> SHA1. Yes? 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