Re: Unexpected behavior during mergeinfo elision scenario

2012-03-27 Thread Stefan Sperling
On Mon, Mar 26, 2012 at 03:15:17PM -0500, John wrote: > $ svn merge --record-only ^/myproject/trunk/subdir@2676 subdir > > $ svn pg 'svn:mergeinfo' subdir > subdir - /myproject/branches/W/subdir:1488-2675 > /myproject/branches/Y/subdir:5925-7118 > /myproject/trunk/subdir:1488-7532 > > $ svn pg 's

Re: Unexpected behavior during mergeinfo elision scenario

2012-03-26 Thread John
On Mon, Mar 26, 2012 at 5:11 AM, Stefan Sperling wrote: > On Fri, Mar 23, 2012 at 04:26:07PM -0500, a nsvnuser wrote: >> svn merge -r 1488:2779 ^/myproject/trunk/subdir subdir >> --- Recording mergeinfo for merge of r1489 through r2675 into 'subdir': >>  U   subdir >> >> svn diff >> [No output] >

Re: Unexpected behavior during mergeinfo elision scenario

2012-03-26 Thread Stefan Sperling
On Fri, Mar 23, 2012 at 04:26:07PM -0500, a nsvnuser wrote: > svn merge -r 1488:2779 ^/myproject/trunk/subdir subdir > --- Recording mergeinfo for merge of r1489 through r2675 into 'subdir': > U subdir > > svn diff > [No output] > In revision 2780 > ^/myproject/trunk was replaced via > a copy f

Unexpected behavior during mergeinfo elision scenario

2012-03-23 Thread a nsvnuser
I have a mergeinfo elision scenario that is behaving in a manner I do not understand. I have a clean checkout of a branch (to eliminate any mixed revision working copy behavior): $ svn co [URL redacted]/myproject/branches/X $ cd X The difference in the mergeinfo, between subdir and subdir/A, is