Re: Issue with order of svn:mergeinfo revision ranges vs. svnmerge-migrate-history.py..
From: Paul Burba <ptburba_at_gmail.com>
Date: Fri, 23 Jan 2009 14:36:30 -0500
On Fri, Jan 23, 2009 at 1:33 PM, Gunter Woytowitz
Gunter,
That's good news in the sense that it keeps the problem in the
> I have just copied the one line of svn:mergeinfo that was corrupted.
For now just two questions:
Do you have any broken history in the path with the range-overlapping
What was the value of the svnmerge-integrated property on the path
> but the short term need is to relax the error checking to allow unordered/overlapping versions on reads of svn:mergeinfo data.
I will look into this today. It's not quite as straight forward as
> BTW, I'm still not clear how a corrupted svn:mergeinfo property can be committed. Does the svnmerge-migrate-history.py script bypass these checks somehow?
It was possible due to a bug in the scripts that was recently fixed:
http://svn.collab.net/viewvc/svn?view=revision&revision=35358
I'm not sure if the svnmerge/svnmerge-migrate-history*.py scripts can
Paul
>
------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.