http://subversion.tigris.org/issues/show_bug.cgi?id=3895
This issue is about rejecting commits that attempt to introduce invalid, i.e. fails to parse, svn:mergeinfo. This has been fixed on trunk and was backported to 1.6.17. It turns out that the fix was incomplete: it didn't fix commits through mod_dav_svn, see issue 3953. I voted for the 3895 backport but I've now realised it causes problems for repositories that already include invalid mergeinfo: they can no longer be copied by dump/load or svnsync. There is no easy way for users to correct the problem. Do we need to provide a way for users to handle such repositories? Force the commit? Delete the mergeinfo? Attempt to correct the mergeinfo? -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
