[svnbook commit] r2593 - branches/ora-2e-reorg/src/en/book

[cmpilato]

Author: cmpilato
Date: Wed Jan  3 11:49:19 2007
New Revision: 2593

Modified:
   branches/ora-2e-reorg/src/en/book/ch-advanced-topics.xml

Log:
* src/en/book/ch-advanced-topics.xml
  (Peg and Operative Revisions): Note the default value for operative
    revisions, too.
  (Selective Versioning): Remove unnecessary word "currently",
    suggested by Ben.


Modified: branches/ora-2e-reorg/src/en/book/ch-advanced-topics.xml
==============================================================================
--- branches/ora-2e-reorg/src/en/book/ch-advanced-topics.xml	(original)
+++ branches/ora-2e-reorg/src/en/book/ch-advanced-topics.xml	Wed Jan  3 11:49:19 2007
@@ -188,10 +188,13 @@
 
       </itemizedlist>
 
-      <para>Not that even when you don't explicitly supply a
-        peg-revision, it's still present.  For your convenience, it
-        defaults to <literal>BASE</literal> for working copy items,
-        and to <literal>HEAD</literal> for repository URLs.</para>
+      <para>Note that even when you don't explicitly supply a peg
+        revision or operative revision, they are still present.  For
+        your convenience, the default peg revision is
+        <literal>BASE</literal> for working copy items and
+        <literal>HEAD</literal> for repository URLs.  And when no
+        operative revision is provided, it defaults to being the same
+        revision as the peg revision.</para>
         
     </sidebar>
 
@@ -255,15 +258,21 @@
 mechanisms.
 </screen>
 
-    <para>This appears to be the right output.  The text even mentions
-      frabbing naggily worts, so this is almost certainly the file
-      which describes the software now called Frabnaggilywort.  In
-      fact, we can verify this using the combination of an explicit
-      peg revision and explicit operative revision.  We know that in
-      <literal>HEAD</literal>, the Frabnaggilywort project is located
-      in the <filename>frabnaggilywort</filename> directory.  So we
-      specify that we want to see how the line of history identified
-      in <literal>HEAD</literal> as the path
+    <para>Notice that we didn't provide an operative revision this
+      time.  That's because when no operative revision is specified,
+      Subversion assumes a default operative revision that's the same
+      as the peg revision.</para>
+
+    <para>As you can see, the output from our operation appears to be
+      correct.  The text even mentions frabbing naggily worts, so this
+      is almost certainly the file which describes the software now
+      called Frabnaggilywort.  In fact, we can verify this using the
+      combination of an explicit peg revision and explicit operative
+      revision.  We know that in <literal>HEAD</literal>, the
+      Frabnaggilywort project is located in the
+      <filename>frabnaggilywort</filename> directory.  So we specify
+      that we want to see how the line of history identified in
+      <literal>HEAD</literal> as the path
       <filename>frabnaggilywort/IDEA</filename> looked in revision
       1.</para>
 
@@ -1243,7 +1252,7 @@
 
     <warning>
       <para>Subversion's support for ignorable file patterns extends
-        only to the one-time process of adding currently unversioned
+        only to the one-time process of adding unversioned
         files and directories to version control.  Once an object is
         under Subversion's watchkeep, the ignore pattern mechanisms no
         longer apply to it.  In other words, don't expect Subversion