From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Tue, 01 Aug 2006 02:36:38 GMT
Subject: Re: Diff format in packs
Message-ID: <46a038f90607311936w17974396h656ace07e365c69b@mail.gmail.com>
In-Reply-To: <9e4733910607311929j189eb6b9r6a804cc744290fdc@mail.gmail.com>

On 8/1/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> On 7/31/06, Martin Langhoff <martin.langhoff@gmail.com> 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