[svnbook commit] r1895 - trunk/src/en/book

maxb svnbook-dev at red-bean.com
Fri Dec 9 05:40:45 CST 2005

Author: maxb
Date: Fri Dec  9 05:40:42 2005
New Revision: 1895


* en/book/appa.xml: Update for current output formats.
  Fix error in TODO comment (it is status -v which needs documenting, not -u).
  Fix plurality typo.

Modified: trunk/src/en/book/appa.xml
--- trunk/src/en/book/appa.xml	(original)
+++ trunk/src/en/book/appa.xml	Fri Dec  9 05:40:42 2005
@@ -249,9 +249,9 @@
       modifications look like this:</para>
-% svn status
-M     ./foo.c
-M     ./bar/baz.c
+$ svn status
+M      foo.c
+M      bar/baz.c
     <para>If you specify the <option>--show-updates</option>
@@ -259,11 +259,11 @@
-% svn status -u
-M             1047    ./foo.c
-       *      1045    ./faces.html
-       *         -    ./bloo.png
-M             1050    ./bar/baz.c
+$ svn status -u
+M            1047   foo.c
+       *     1045   faces.html
+       *            bloo.png
+M            1050   bar/baz.c
 Status against revision:   1066
@@ -273,11 +273,11 @@
       item.  In the example above, the asterisk indicates that
       <filename>faces.html</filename> would be patched if we updated,
       and that <filename>bloo.png</filename> is a newly added file in
-      the repository.  (The <literal>-</literal> next to
+      the repository.  (The absence of any revision number next to
       <filename>bloo.png</filename> means that it doesn't yet exist in
       the working copy.)</para>
-    <!-- ###TODO describe -u here as well as -uv. -u and -v use
+    <!-- ###TODO describe -v here as well as -uv. -u and -v use
          different <quote>long</quote> formats and need to be
          documented separately. Moreover, as you can combine -u and
          -v, it needs to be explained what each of them does. As -u is
@@ -484,7 +484,7 @@
       directory) unless you tell it not to by using the
       <option>--no-auth-cache</option> switch.</para>
-    <para>The exception to this behaviors, however, is in the case of
+    <para>The exception to this behavior, however, is in the case of
       accessing an <command>svnserve</command> server over an SSH
       tunnel, using the <literal>svn+ssh://</literal> URL schema.  In
       that case, the <command>ssh</command> program unconditionally

More information about the svnbook-dev mailing list