[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion 1.6.7 on Dec. 16.

From: Paul Burba <ptburba_at_gmail.com>
Date: Fri, 18 Dec 2009 17:27:28 -0500

On Fri, Dec 18, 2009 at 5:01 PM, Branko Čibej <brane_at_xbc.nu> wrote:
> Philip Martin wrote:
>> Paul Burba <ptburba_at_gmail.com> writes:
>>
>>> So shouldn't the mergeinfo on this path in the old repos,
>>>
>>>
>>>> svn pg svn:mergeinfo https://svn.collab.net/repos/svn/branches/1.6.x-r40452/CHANGES@40513
>>>>
>>> ...
>>> /trunk/CHANGES:2-1281,35888-40052,40088,40152,40451-40452
>>>
>>> differ from from the new repos,
>>>
>>>
>>>> svn pg svn:mergeinfo https://svn.apache.org/repos/asf/subversion/branches/1.6.x-r40452/CHANGES@880587
>>>>
>>> ...
>>> subversion/trunk/CHANGES:836421-837700,872307-876471,876507,876571,880525-880526
>>>
>>> only by the offset?  The fact that it doesn't is troubling, to say the
>>> least, and might also explain why you got different results with the
>>> old repos.
>>>
>>
>> Yes, I think you are right and I don't understand it.
>>
>
> I find this quite disturbing ... although it has no direct bearing on
> whether the merge bug is a new bug or not, we should still figure out
> how this mergeinfo got out of sync.
>
> (BTW, all the above pretty much convinced me that this merge failure
> indeed is not a new bug.)
>
> -- Brane

I agree and will be trying to figure out what happened Monday.

Paul
Received on 2009-12-18 23:28:05 CET

This is an archived mail posted to the Subversion Dev mailing list.