Re: started a cvsps testsuite Was: Re: [PATCH v3 0/2] cvsimport: add test illustrating a bug in cvsps

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Mar 23, 2009, 19:06 UTC
Message-ID: <46a038f90903231206i9f1dde2pb12fab3764e55cbd@mail.gmail.com>
In-Reply-To: <20090323181110.GB26678@macbook.lan>

On Mon, Mar 23, 2009 at 7:11 PM, Heiko Voigt <hvoigt@hvoigt.net> wrote:

> I just started a very simple but hopefully effective testsuite to
> collect all the issues we found with cvsps.

Excellent effort. One thing I found when I was debugging (and trying to understand) corner cases in cvs imports was the test suite for the cvs2svn importer. It had a number of tiny cvs repositories that were broken in various ways.

The test cvs repos, straight from the svn repo for cvs2svn are in http://cvs2svn.tigris.org/svn/cvs2svn/trunk/test-data/ - access with user:guest and an empty password.

...

> Hopefully we can collect some more specifics about the situations where
> cvsps fails and most importantly the amount of coding needed for fixing.
> From there on it should be easier to decide which route to follow for
> a robust inbuild git cvsimport.

Some cvs repos are ambiguous. Others are "impossible", fruits of direct file manipulation. cvs2svn has a fairly robust (and inordinately slow!) approach, but you cannot rerun it to get incremental imports.

It is certainly possible... and bloody hard!

cheers,

-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff