2009/5/30 Nick Woolley <nickwoolley@xxxxxxxxxxx>: > Hi, > > I have script which wraps git-cvsimport and git-cvsexport, called "git-cvs". > > The main aim of the script is to automate the steps for tracking a CVS > repository with the git-cvs* commands. > > It's not currently as sophisticated as git-svn, it's undoubtably flawed and > isn't foolproof (e.g. exports to CVS of merged git histories can be > problematic), but I find it useful, because a lot of the nitty-gritty is done > for me. > > I'd like to ask: > > - Is this at all useful to anyone else in it's current form? If this is using the inbuilt cvsps and perl then it will likely choke on very large CVS repos. For some CVS tree's I've had to resort to a hacked up version of parsecvs to get a conversion running. The other repo it tends to die on is ones which have been pruned (i.e. old branches have been cut off). But people there have made a decision to mess with their repo. > - Written in Perl, uses only core modules (tested with v5.8.8) > > - There is a small test suite in t/, run individually or with "prove/*.t" > I'll give your script a spin on the repo I have here and I'll report on how it does :-) -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php -- 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