Author: philip
Date: Sat Feb 14 16:45:41 2015
New Revision: 1659810

URL: http://svn.apache.org/r1659810
Log:
* STATUS: Remove veto from svnsync r0 mergeinfo fix.

Modified:
    subversion/branches/1.8.x/STATUS

Modified: subversion/branches/1.8.x/STATUS
URL: 
http://svn.apache.org/viewvc/subversion/branches/1.8.x/STATUS?rev=1659810&r1=1659809&r2=1659810&view=diff
==============================================================================
--- subversion/branches/1.8.x/STATUS (original)
+++ subversion/branches/1.8.x/STATUS Sat Feb 14 16:45:41 2015
@@ -153,6 +153,18 @@ Candidate changes:
      +1: rhuijben, julianfoad (without r1659801)
      +1: philip
 
+ * r1646230, r1646250, r1646253, r1656893, r1657182, r1657195, r1657401
+   Make svnsync strip any r0 references from mergeinfo -- issue #4476.
+   Justification:
+     Without this is was not possible to svnsync a repository that contained
+     this kind of mergeinfo that is now considered invalid but previously
+     could be committed.
+   Notes:
+     This is also nominated for 1.7.x. The regression test in this group
+     depends on the issue #4538 fix in r1646505.
+   Votes:
+     +1: julianfoad, philip
+
 Veto-blocked changes:
 =====================
 
@@ -166,21 +178,6 @@ Veto-blocked changes:
      +1: stsp
      -1: breser (see my email to dev@, <[email protected]>)
 
- * r1646230, r1646250, r1646253, r1656893, r1657182, r1657195, r1657401
-   Make svnsync strip any r0 references from mergeinfo -- issue #4476.
-   Justification:
-     Without this is was not possible to svnsync a repository that contained
-     this kind of mergeinfo that is now considered invalid but previously
-     could be committed.
-   Notes:
-     r1643074 (nominated separately) is required for the test to work.
-     I would recommend not backporting r1646250 without r1643074.
-     This is also nominated for 1.7.x. The regression test in this group
-     depends on the issue #4538 fix in r1646505.
-   Votes:
-     +1: julianfoad
-     -1: philip (new test is a FAIL, needs a fix for issue 4538)
-
 Approved changes:
 =================
 


Reply via email to