Re: cvs2git reports a "sprout" from a nonexistent commit? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: cvs2git reports a "sprout" from a nonexistent commit?
Date
Msg-id 13470.1284393159@sss.pgh.pa.us
Whole thread Raw
In response to Re: cvs2git reports a "sprout" from a nonexistent commit?  (Michael Haggerty <mhagger@alum.mit.edu>)
List pgsql-hackers
Michael Haggerty <mhagger@alum.mit.edu> writes:
> On 09/13/2010 03:14 AM, Tom Lane wrote:
>> Now as far as I can tell, the branch was made immediately before those
>> test commits you can see Marc making in each branch.  In particular,
>> it was definitely made *after* Bryan deleted the src/bin/monitor files,
>> because neither of them have REL2_0 or REL2_0B tags.  So why did cvs2git
>> choose to sprout the branch from the commit before that, and have to
>> duplicate the deletion of the files?

> This is a known bug 139 [1] in cvs2git's symbol parent choosing code 
> (previously mentioned as part of bug 55 [2]).  Patches are welcome :-)

Thanks for the response.  Since this bug causes only one very minor
infelicity in our conversion, probably nobody here is going to be
motivated to fix it.  OTOH, I'm still annoyed by the behavior for
addition of files to back branches ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Report: removing the inconsistencies in our CVS->git conversion
Next
From: Greg Smith
Date:
Subject: Re: Perf regression in 2.6.32 (Ubuntu 10.04 LTS)