On Fri, Oct 5, 2012 at 7:12 AM, C. Michael Pilato <cmpil...@collab.net> wrote: > That's right. Expat just doesn't care. Some other XML parser might. But > then, I would expect that same parser would croak on any property name with > a colon in it (besides "svn:", which we handle specially already). So all > of TortoiseSVN's properties, cvs2svn's properties, etc. -- all that stops > working.
[snip] > I don't think so. I think that would be just a lovely instance of the > perfect being the enemy of the good [enough]. If it becomes a real-world > problem, our recourse is rather straightforward -- we continue our move away > from the DAV standard and implement our own custom POST/REPORT handling. My memory is fuzzy on this and it's been 5-6 years but ISTR that the problem was with people using auto versioning since the XML wouldn't be valid. -1: On just doing this and hoping for the best. If it really is auto versioning that breaks due to this, it is a supported feature of our code set and not one that I suspect any of us test very often. If we test auto versioning with the most commonly used configs and we have no issues then I'd be +0.
