Re: svn merge --reintegrate trouble again
From: Reid Priedhorsky <reid_at_umn.edu>
 
Date: Thu, 05 Mar 2009 13:17:59 -0600 
On 03/05/2009 09:48 AM, Mark Phippard wrote:
 I think so. I didn't create it, but our internal docs say to use the 
  > From what revision of trunk?
 Looks like r9688. (That's the greatest revision of the trunk less than 
  > Was it possibly created from a mixed-revision WC of trunk?
 I think it's unlikely. We don't deliberately create mixed-revision WC's. 
 The $svnroot on the machine where the branch was created could be a 
 > Let's assume the branch was created by copying trunk at rN.  Then the
 Is it true that the plain svn merge above is equivalent to (HEAD was 
 $ svn merge $svnroot/br/masli_ib-misc_820_at_9696 
 and the svn --reintegrate was equivalent to
 $ svn merge $svnroot/trunk_at_9688 $svnroot/br/masli_ib-misc_820_at_9737
 However,
 $ svn diff $svnroot/trunk_at_9688 $svnroot/br/masli_ib-misc_820_at_9696
 is empty, and
 $ svn diff $svnroot/br/masli_ib-misc_820_at_9696 
 and
 $ svn diff $svnroot/trunk_at_9688 $svnroot/br/masli_ib-misc_820_at_9737
 produce identical diffs (except for the notations about paths and 
 So it seems that in this case, svn merge and svn merge --reintegrate 
 Is there some way to get a debug trace from svn merge? It does not 
 Much appreciated,
 Reid
 ------------------------------------------------------
 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.