svn commit: r1544896 - /subversion/branches/1.8.x/STATUS

[rh...@apache.org]

Author: rhuijben
Date: Sun Nov 24 00:36:08 2013
New Revision: 1544896

URL: http://svn.apache.org/r1544896
Log:
Move r1544597 group to proper location. Extend r1544878 group and cast vote.

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=1544896&r1=1544895&r2=1544896&view=diff
==============================================================================
--- subversion/branches/1.8.x/STATUS (original)
+++ subversion/branches/1.8.x/STATUS Sun Nov 24 00:36:08 2013
@@ -162,12 +162,30 @@ Candidate changes:
    Votes:
      +1: breser, brane
 
- * r1544878
-   Fix output of svn --version -v to not cut info off.
+ * r1544597, r1544600, r1544688, r1544690
+   Fix a specific case where the api behind status would report a different
+   move status for A depending on whether the user called 'svn status A' or
+   'svn status wc/A'.
+   Justification:
+     Api users such as AnkhSVN rely in the result of svn status and this
+     breaks their assumptions.
+     This change has the nice side effect that it resolves the most common
+     user triggerable assertion in AnkhSVN, which is really caused by a
+     broken move. (See other nomination for a fix). But even then it shouldn't
+     matter how status is called: on the node or an ancestor.
+     (It also improves status performance a tiny bit, by reducing the number
+      of sqlite transactions used)
+   Votes:
+     +1: rhuijben
+
+ * r1544878, r1544895
+   Fix output of svn --version -v to not cut info off on linux.
    Justification:
      Obviously wrong.
+   Notes:
+     The relevant code is #ifdeffed out on anything but linux.
    Votes:
-     +1: breser
+     +1: breser (without r1544895), rhuijben
 
 Veto-blocked changes:
 =====================
@@ -196,21 +214,5 @@ Veto-blocked changes:
      -1: breser (includes a --keep-going test which fails on 1.8.x since no
                  such option in 1.8.x)
 
- * r1544597, r1544600, r1544688, r1544690
-   Fix a specific case where the api behind status would report a different
-   move status for A depending on whether the user called 'svn status A' or
-   'svn status wc/A'.
-   Justification:
-     Api users such as AnkhSVN rely in the result of svn status and this
-     breaks their assumptions.
-     This change has the nice side effect that it resolves the most common
-     user triggerable assertion in AnkhSVN, which is really caused by a
-     broken move. (See other nomination for a fix). But even then it shouldn't
-     matter how status is called: on the node or an ancestor.
-     (It also improves status performance a tiny bit, by reducing the number
-      of sqlite transactions used)
-   Votes:
-     +1: rhuijben
-
 Approved changes:
 =================