You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by cm...@apache.org on 2011/12/19 16:12:19 UTC

svn commit: r1220784 - /subversion/branches/1.7.x/STATUS

Author: cmpilato
Date: Mon Dec 19 15:12:18 2011
New Revision: 1220784

URL: http://svn.apache.org/viewvc?rev=1220784&view=rev
Log:
Propose r1215260 and friends for backport.

Modified:
    subversion/branches/1.7.x/STATUS

Modified: subversion/branches/1.7.x/STATUS
URL: http://svn.apache.org/viewvc/subversion/branches/1.7.x/STATUS?rev=1220784&r1=1220783&r2=1220784&view=diff
==============================================================================
--- subversion/branches/1.7.x/STATUS (original)
+++ subversion/branches/1.7.x/STATUS Mon Dec 19 15:12:18 2011
@@ -103,6 +103,31 @@ Candidate changes:
    Votes:
      +1: stsp, philip
 
+ * r1215260, r1215374, r1215375, r1215379
+   Fix issue #4082 ("'svn log --with-all-revprops' over ra-dav
+   intolerant of XML-unsafe property values").
+   Justification:
+     'Tis better to succeed than to fail.  Unless of course you're
+     talking about successfully doing evil, in which case 'tis better
+     to fail.  But we're not talking about doing evil here.  Unless
+     you think XML is evil.  But seriously, these commits introduce a
+     protocol change for WebDAV.  I suspect that might disqualify it
+     in some folks' eyes from backport to a patch release rather
+     automatically.  But the protocol change is (as all our other
+     protocol changes are) designed to maintain compatibility across
+     client and server versions.  If the client advertises support for
+     the new behavior, and the server has such support, the bugfix
+     logic is activitated.  A patched client will not trouble an
+     unpatched server; nor vice-versa.  Further, the effects of the
+     corrected behavior do not persist, so there's no dataset damage
+     imposed for users who would roll this change back out of their
+     systems (by reverting to a prior release).  Therefore, cmpilato
+     can't think of a good reason not to backport the change.
+   Notes:
+     A backport branch (coming soon!) is required for a clean merge.
+   Votes:
+     +1: cmpilato
+
  * r1220742, r1220750
    Fix spurious testsuite FAIL
    Justification: