From: Adam Mercer <ramercer@gmail.com>
Date: Fri, 23 May 2008 20:24:40 GMT
Subject: Re: git cvsimport error
Message-ID: <799406d60805231324o209692d2o59a700024e52100c@mail.gmail.com>
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F794301FC8BCA@emailmn.mqsoftware.com>

On Fri, May 23, 2008 at 3:05 PM, Craig L. Ching <cching@mqsoftware.com> wrote:
> Yeah, I don't know much about it at all, but my advice would be to run
> cvsps by itself and generate a cache that git-fast-import can import.
> That's the approach we're taking because it gives us a chance to figure
> out where things have gone wrong as we have some bad, buggy commits in
> our archive (CVS created the bad commits).

I thought of using git-fast-import but the problem is that the CVS
repository is still in use so I need to keep the git and CVS repos
synchronised and it seems like git-fast-import can't be used in this
case.

Cheers

Adam