Re: now with more agressive elision (was: [PATCH] svn mergeinfo --elide)
From: Paul Burba <ptburba_at_gmail.com>
Date: Sat, 10 Sep 2011 14:08:38 -0400
On Sat, Sep 10, 2011 at 1:07 PM, Stefan Sperling <stsp_at_elego.de> wrote:
No, rather, "non-inheritable ranges only apply to nodes which *DO*
Say a path src/branches/b1 has the mergeinfo:
r1200 applies only to src/branches/b1, the path on which it is
I'm pretty sure you already know this, it's just that we keep using
> And any subtree mergeinfo overrides the mergeinfo
Yes, that is all I was trying to say. If a path has explicit
> In which ways do you think automatic elision needs to be improved?
A path P and some path-wise child of P called C:
Can the mergeinfo on C elide to P?
Looking at the intersection of the P and C's mergeinfo we have:
A) Common mergeinfo (that differs only by the path-wise difference
B) Mergeinfo exclusive to P - If *all* of this describes merges that
C) Mergeinfo exclusive to C - If all of this describes merges that are
If elision occurs in *all* three cases then the mergeinfo on C can elide to P.
Today only 'A' is supported when 'B' and 'C' are empty sets.
> Do you think there is value in adding just 'svn mergeinfo --elide'
Yes, I think the basic idea is sound: Some way to trigger the elision
This is an archived mail posted to the Subversion Dev mailing list.