Re: Call for testing: cvs2bzr

On Thu, Aug 20, 2009 at 5:48 PM, Michael Haggerty<[email protected]> wrote:
> What kind of time scale are we talking about for you to submit the
> patches?  Days?  Weeks?  (Not that I can promise to review them
> immediately :-( )

Several days, possibly up to a week.  You can see I'm submitting them
as I prepare them, but it'll take time to polish everything.
Especially the help and documentation.  So if you want to meet the
Ubuntu freeze deadline, don't wait for me.  It sounds like you've got
enough nice changes queued up to make 2.3 worthwhile even without my
cvs2hg.

>>   * 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)
>
> I think that it already returns the suggested parent revisions in
> approximate best-to-worst order, measured by how many file revisions can
> be taken from each suggested parent.

That's roughly what I had in mind.  Maybe we just need to codify
current behaviour in the docstring and make sure the data isn't being
scrambled by going through a dict.  But please hold off: that method
is one of the things I'm moving from git_output_option.py to
dvcs_common.py, and changes to it will just give me merge conflicts.
Relevant patches coming over the weekend, I hope!

Greg

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

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