On Mon, Mar 23, 2009 at 7:11 PM, Heiko Voigt <hvoigt@xxxxxxxxxx> 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, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
