You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by rh...@apache.org on 2014/03/20 09:52:04 UTC
svn commit: r1579564 - /subversion/branches/1.8.x/STATUS

Author: rhuijben
Date: Thu Mar 20 08:52:04 2014
New Revision: 1579564

URL: http://svn.apache.org/r1579564
Log:
* STATUS: Cast vote. Approve r1574868.

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=1579564&r1=1579563&r2=1579564&view=diff
==============================================================================
--- subversion/branches/1.8.x/STATUS (original)
+++ subversion/branches/1.8.x/STATUS Thu Mar 20 08:52:04 2014
@@ -181,24 +181,6 @@ Candidate changes:
    Votes:
      +1: rhuijben, philip
 
- * r1574868
-   Don't let invalid mergeinfo stop 'svnadmin dump' from producing a dump.
-     Part of issue #4476 "Mergeinfo containing r0 makes svnsync and svnadmin
-     dump fail".
-   Justification:
-     A formatting error in what is essentially client-side metadata, albeit
-     with repository-side interpretation as well, should never prevent
-     dumping the repository. This issue only occurs when svnadmin is trying
-     to warn us of mergeinfo revisions that might be unexpected, so it is
-     not essential.
-   Notes:
-     There is a work-around, at least in theory: a dump starting from
-     revision 0 or 1 does not suffer from this problem.
-   Branch:
-     ^/subversion/branches/1.8.x-r1574868
-   Votes:
-     +1: julianfoad, philip
-
  * r1575525, r1575915
    Resolve issue #4427: File externals can't be exported.
    Justification:
@@ -304,3 +286,21 @@ Veto-blocked changes:
 
 Approved changes:
 =================
+
+ * r1574868
+   Don't let invalid mergeinfo stop 'svnadmin dump' from producing a dump.
+     Part of issue #4476 "Mergeinfo containing r0 makes svnsync and svnadmin
+     dump fail".
+   Justification:
+     A formatting error in what is essentially client-side metadata, albeit
+     with repository-side interpretation as well, should never prevent
+     dumping the repository. This issue only occurs when svnadmin is trying
+     to warn us of mergeinfo revisions that might be unexpected, so it is
+     not essential.
+   Notes:
+     There is a work-around, at least in theory: a dump starting from
+     revision 0 or 1 does not suffer from this problem.
+   Branch:
+     ^/subversion/branches/1.8.x-r1574868
+   Votes:
+     +1: julianfoad, philip, rhuijben