RE: Spurious svn:mergeinfo updated on random, untouched files on minimalistic merge?! -- SOLVED !!!
From: Ben <tebulin_at_googlemail.com>
Date: Wed, 31 Mar 2010 16:22:37 +0200
Geoff - Thank you very much for your extensive advice of how to avoid
My problem was not any existing svn:mergeinfos. Neither the source nor
My problem was:
I have no clue how this occured. We *never* do partial chechkouts, but a
After recovering the partial state all works as expected.
Thanks a lot to everybody for your time and support!
In addition to adding merge info to your working copy target, merge info
The only way to correct this is to consolidate the merge info into the
To avoid an increasing number of items with this property, as a result
The Subversion Hook Framework can be used to enforce this policy.
There's an example of the required configuration (XML) file entry on the
This is an archived mail posted to the Subversion Users mailing list.