Re: Call for testing: cvs2bzr

On Thu, Aug 20, 2009 at 5:02 PM, Michael Haggerty<[email protected]> wrote:
> What would be the deadline to get into karmic?  It would be nice if the
> new and improved cvs2hg were included in release 2.3.0, if that is at
> all realistic.
>
> Greg?  Do you have any idea of an ETA for cvs2hg?

It's been arriving for a few days now... that's what those patches
I've been sending are.  ;-)

But seriously: I've paused active development to concentrate on
sending you patches because 1) I don't want to drift too far from
upstream, 2) I really need to concentrate on the actual CVS conversion
I'm doing at work, and 3) cvs2hg in its current form appears to be
mostly good enough.  At any rate it is correct, performs adequately,
and is (mostly) well-behaved in its memory usage.  IOW, once we get my
patches integrated into your tree, I'd be happy to see cvs2hg go out
in a real release.

There are still things I'd like to do, though:

  * have more options for how to create fixup commits
  * take a stab at making get_source_groups() guess the "best fit"
parent revision of a fixup (which will benefit cvs2git and cvs2bzr as
well)
  * figure out why the heck the memory usage is so different between
Mercurial 1.2 and 1.3
  * try to sort the revisions for a space-efficient hg repository

Apart from the first, those are all fairly difficult and not on my
critical path at work, though, so don't hold your breath waiting for
them.

Oh yeah, I need to write some docs too.  I've started
(http://vc.gerg.ca/hg/cvs2svn/file/tip/README.cvs2hg), but that should
really be www/cvs2hg.html, right?

Greg

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2385802

To unsubscribe from this discussion, e-mail: [[email protected]].