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

Issue with order of svn:mergeinfo revision ranges vs. svnmerge-migrate-history.py..

From: Clark, Rob <rob_at_ti.com>
Date: Wed, 10 Sep 2008 11:37:10 -0500

This might be something that depended on which version of svnmerge.py you
have, but it seems like svnmerge-migrate-history.py can put discontinuous
revision ranges in the wrong order (ie. '13322-13324,13320' instead of
'13320,13322-13324'). I've been manually fixing this in the latest revision
when merging branches and getting errors, but now I'm running into the issue
that 'svn log -g' is getting tripped up on some older revision:

   Exception: svn: Unable to parse unordered revision ranges '13322-13324'
and '13320'

So now I'm not really sure how to track down the past revisions that need to
be corrected.

I'm not sure if someone has a fix-svnmerge-migrated-history.py script ;-)

Or any other suggested way to fix this?


(btw, please CC me on reply, I'm not subscribed to the list)

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-10 21:40:17 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.