On Thu, Jun 09, 2011 at 01:42:33PM +0100, Echlin, Jamie wrote: > Hi Johan, > > > This is normal behavior of svn currently. Every subtree that > > already has "explicit mergeinfo" (meaning it has its own svn:mergeinfo > > property) will have that mergeinfo updated on every subsequent merge. > > That is done because it needs to be kept up to date. > > Thanks for your response. > > BTW, http://www.collab.net/community/subversion/articles/merge-info.html > is my mergeinfo bible, I have literally pored over every word, in > excruciating detail. > > The issue is that neither the source nor the target branches have > mergeinfo on the sub-directories already, this merge introduces it. And > this issue has only started happening in the last few weeks. > > > If a node doesn't have mergeinfo of its own, it inherits it from its > parent directory. > > But not always... Under what circumstances does a sub-tree start to get > explicit mergeinfo? As I said, I know a few cases where it happens and > is required, but these don't seem to apply.
Hmmm... Does the parent of the offending directory have non-inheritable mergeinfo? (Mergeinfo entries that have an asterisk appended are not inheritable.)
