Re: Turning cvs2{svn,git} into cvs2hg
Dirkjan Ochtman <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.devel |
|---|---|
| Message-ID | <ea2499da0907190944yb7dc24cn117cdef6a87ccda0__32512.6507356346$1248028950$gmane$org@mail.gmail.com> |
On Sun, Jul 19, 2009 at 18:03, Greg Ward<[email protected]> wrote: > Yes and yes. hg-fastimport is heavily based on bzr-fastimport. (Much > of the work I have done is in extracting a common library, rather than > maintaining a fork of an old version of the parser in bzr-fastimport.) Is there take-up on the bzr-fastimport side of things for that? > Hard to say. There probably would be if it worked better. > Installation/setup is tricky right now because of the dependency on > pyfastimport (the common library that I factored out). Not sure of > the best way to improve that. Include a copy in-tree? Use hg subrepos. ;) > Anyways: rather than making users play follow-the-repo, why don't I > just give you write access to the bitbucket mirror? Do you have a > bitbucket account? Well, I think I'll decline for now. I'm still trying to manage the Python hg migration, and so a bunch of my devel time has been going into hgsubversion. Since you're handling the CVS side, I think the SVN side will be more fertile ground for potential converts than the other DVCSs (for the near future, anyway). Cheers, Dirkjan (djc on Bitbucket, btw) ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2372441 To unsubscribe from this discussion, e-mail: [[email protected]].