Re: cvs2svn conversion directly to git ready for experimentation

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Aug 2, 2007, 23:08 UTC
Message-ID: <46a038f90708021608o21480074ybcfada767afc7b04@mail.gmail.com>
In-Reply-To: <46B1F96B.7050107@alum.mit.edu>

On 8/3/07, Michael Haggerty <mhagger@alum.mit.edu> wrote:

Show 9 quoted lines

> cvsps is not a conversion tool at all, though it is used by other
> conversion tools to generate the changesets.  It appears (I hope I am
> not misinterpreting things) to emphasize speed and incremental
> operation, for example attempting to make changesets consistent from one
> run to the next, even if the CVS repository has been changed prudently
> between runs.  cvsps does not appear to attempt to create atomic branch
> and tag creation commits or handle CVS's special vendorbranch behavior.
>  cvsps operates via the CVS protocol; you don't need filesystem access
> to the CVS repository.

100% in agreement. And though I can't claim to be happy with cvsps, in
many scenarios it is mighty useful, in spite of its significant warts.
 The "does incrementals" is hugely important these days, as lots of
people use git to run "vendor branches" of upstream projects that use
CVS.

To me, that's *the* killer-app feature of git. Of course, others see different aspects of git as their deal-maker. But I'm sure I'm not alone on this. Surely enough, others have written git-svn which accomplishes this and more for those tracking SVN upstreams.

Is there any way we can run tweak cvs2svn to run incrementals, even if not as fast as cvsps/git-cvsimport? The "do it remotely" part can be worked around in most cases.

cheers,

martin