Call for testing: cvs2bzr

[Michael Haggerty]

Ian Clatworthy wrote:
> I've made a patch to cvs2svn so that it includes a new cvs2bzr script.
> I'd like to get this script included upstream but it needs some testing
> first from people with real CVS repositories. A Bazaar branch with the
> patch included is available here:
> https://code.launchpad.net/~ian-clatworthy/+junk/cvs2svn.

On a quick overview, your patch looks reasonable.  The only difference I
see from cvs2git is the use of inline blobs and, basically, s/git/bzr/.
 Is that all that is needed to support cvs2bzr?  (If so, cool!)

Let me know when you would like me to pull this patch.  I would have a
pretty low acceptance threshold, since it doesn't involve much code and
there currently is no cvs2bzr at all.  But there are a few other things
that would be nice:

* A www/cvs2bzr.html page (or perhaps a shared www/cvs2fast-import.html
web page).

* A patch to contrib/verify-cvs2svn.py to allow it to verify cvs2bzr
conversions.  Greg Ward has already abstracted out the parts that vary
from VCS to VCS.  (Ultimately we should develop at least some minimal
test suite for checking non-2svn conversions.)

* A cvs2bzr-example.options file.

When Greg Ward is further along on cvs2hg [1], we should think about
refactoring the common code a little better, maybe s/Git/FastImport/ and
make git, bzr, and hg all peers that derive from the shared code.

Michael

[1] http://vc.gerg.ca/hg/cvs2svn/