RE: Fwd: svn1.5 seems to fail simple merge-tracking scenario
From: Trent Nelson <tnelson_at_onresolve.com>
Date: Thu, 11 Jun 2009 20:51:35 +0100
> On Mon, Jun 8, 2009 at 9:22 AM, Trent
Eek. We've been using the --record-only -r0:100 pattern for the last few months. It seemed to work fine, initially. Only in the last week or two has it become apparent that the last 50+ re-integrations/syncs have almost all been subtlety borked. And in some cases, not so subtlety -- the epic-fail-upon-any-form-of-merge branches are what alerted us to the underlying issue that's been secretly haunting us since we clocked revision ~73 or so, in March-ish.
But, for now, I digress. I've just played around with a couple of re-integrations/syncs using -c 100 instead of -r0:100. This behaviour surprised me:
branches/foo>svn pg svn:mergeinfo . | grep trunk
branches/foo>svn merge --record-only -c 300 ^/trunk
I was expecting to see `trunk:2-115,300`, not `trunk:300`. The latter just doesn't seem right; or am I incorrectly expecting svn:mergeinfo to mirror the semantics of svnmerge-integrated/svnmerge-blocked?
Trent.
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
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.