Re: cvs2svn conversion directly to git ready for experimentation

From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Aug 2, 2007, 15:34 UTC
Message-ID: <46B1F96B.7050107@alum.mit.edu>
In-Reply-To: <8b65902a0708010438s24d16109k601b52c04cf9c066@mail.gmail.com>

[I am CCing this response to the mailing lists.]

Guilhem Bonnefille wrote:

Show 7 quoted lines

> On 8/1/07, Michael Haggerty <mhagger@alum.mit.edu> wrote:
>> I am the maintainer of cvs2svn[1], which is a program for one-time
>> conversions from CVS to Subversion.  cvs2svn is very robust against the
>> many peculiarities of CVS and can convert just about every CVS
>> repository we have ever seen.
> 
> What are the differences with cvsps ( http://www.cobite.com/cvsps/ )?

I'm not extremely familiar with cvsps, and I don't really want to get into a "my-tool-is-better-than-your-tool" kind of argument. Instead I will mention that the goals of the two projects are somewhat different:

cvs2svn is meant for one-time conversions from CVS, and therefore aims for maximum conversion accuracy, robustness even in the presence of some kinds of CVS repository corruption, intelligent translation of CVS idioms to the idioms of a modern SCM, and scalability to large repositories (by using on-disk databases instead of RAM for intermediate data). Conversion speed is not a primary goal of cvs2svn, and incremental conversions are not supported at all. cvs2svn requires filesystem access to the CVS repository (it parses the RCS files directly).

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.

I can also point you to a list of cvs2svn features, which includes a list of some of the CVS quirks that it knows how to handle:

    http://cvs2svn.tigris.org/cvs2svn.html#features

cvs2svn includes a large suite of perverse CVS repositories that we use for testing. Many of them are derived from real-life CVS repositories that people have had problems with. It would be very interesting to see how other conversion tools handle these repositories, but I don't expect to have time to do so in the near future.

Michael