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

fitz noreply at red-bean.com
Sat Dec 8 16:38:55 CST 2007


Author: fitz
Date: Sat Dec  8 16:38:53 2007
New Revision: 2904

Log:
Refine explanation about 'svn commit ; svn log'.

Thanks to Ben for the clarity.

* src/en/book/ch02-basic-usage.xml: I call him my "Little Chef".


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:38:53 2007
@@ -1567,17 +1567,16 @@
           messages.  This is due to a combination of the behavior of
           <command>svn commit</command> and the default behavior of
           <command>svn log</command>.  First, when you commit changes
-          to the repository, only the files (and directories) that you
-          changed are <quote>updated</quote> to the latest revision,
-          so unless you updated a property on your current directory,
-          your commit leaves that directory <quote>out of
-          date</quote>.  When you run <command>svn log</command> with
-          no arguments, it takes the latest revision from your current
-          working directory, which is out of date, so you don't see
-          your latest commit.  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>
+          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>
 
       </sidebar>
 




More information about the svnbook-dev mailing list