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

[fitz]

Author: fitz
Date: Sat Dec  8 16:42:08 2007
New Revision: 2905

Log:
Link to more info on svn commit's behavior.

Thanks to Ben for waiting until I made the last commit to send this
great suggestion.

* src/en/book/ch02-basic-usage.xml: Florp.


Modified:
   trunk/src/en/book/ch02-basic-usage.xml

Modified: trunk/src/en/book/ch02-basic-usage.xml
==============================================================================
--- trunk/src/en/book/ch02-basic-usage.xml	(original)
+++ trunk/src/en/book/ch02-basic-usage.xml	Sat Dec  8 16:42:08 2007
@@ -1569,14 +1569,16 @@
           <command>svn log</command>.  First, when you commit changes
           to the repository, <command>svn</command> only bumps the
           revision of files (and directories) that it commits, so
-          usually the parent directory remains at the older revision.
-          <command>svn log</command> then defaults to fetching the
-          history of the directory at its current revision, and thus
-          you don't see the newly-committed changes.  The solution
-          here is to either update your working copy or explicitly
-          provide a revision number to <command>svn log</command> by
-          using the <option>--revision</option> (<option>-r</option>)
-          option.</para>
+          usually the parent directory remains at the older revision
+          (See <xref
+          linkend="svn.basic.in-action.mixedrevs.update-commit"/> for
+          why).  <command>svn log</command> then defaults to fetching
+          the history of the directory at its current revision, and
+          thus you don't see the newly-committed changes.  The
+          solution here is to either update your working copy or
+          explicitly provide a revision number to <command>svn
+          log</command> by using the <option>--revision</option>
+          (<option>-r</option>) option.</para>
 
       </sidebar>