Paul Burba wrote: > Regardless, I don't think this is a true regression, just a > new bug, and as such, not something that should hold up 1.6.7. >
Sorry, what? Subversion will suddenly error out where it previously did not. No matter /how/ that mergeinfo got into the repository, if we don't fix this before releasing 1.6.7, we'll likely get a whole bunch of error reports. Telling people that "it's not really a bug" isn't going to be very productive, given that it effectively stops them from using svn merge in this situation. Can you be sure that the circumstances that lead to this error are rare enough to address in 1.6.8? -- Brane
