[svnbook] r4078 committed - Read-thru edits....
svnbook at googlecode.com
svnbook at googlecode.com
Thu Sep 8 13:49:43 CDT 2011
Revision: 4078
Author: cmpilato at gmail.com
Date: Thu Sep 8 11:48:49 2011
Log: Read-thru edits.
* en/book/ch03-advanced-topics.xml
(svn.advanced.pegrevs): Remove a stray character recently added.
(svn.advanced.props): Minor tweaks.
(svn.advanced.sparsedirs, svn.advanced.externals): Tweak wording to
not imply that 1.6 is the "current" offering.
(svn.advanced.locking.creation): Update 'svn info' output to
include 'Repository Root' and 'Working Copy Root Path' items.
(svn.advanced.locking.discovery): Update 'svn info' output to
include 'Repository Root' item.
http://code.google.com/p/svnbook/source/detail?r=4078
Modified:
/trunk/en/book/ch03-advanced-topics.xml
=======================================
--- /trunk/en/book/ch03-advanced-topics.xml Tue Sep 6 14:02:35 2011
+++ /trunk/en/book/ch03-advanced-topics.xml Thu Sep 8 11:48:49 2011
@@ -438,7 +438,7 @@
sorts, and we know <emphasis>exactly</emphasis> where to
go.</para>
- <sidebar>
+ <sidebar id="svn.advanced.pegrevs.algorithm">
<title>The Peg Revision Algorithm</title>
<para>The Subversion command-line client performs the peg revision
@@ -559,7 +559,7 @@
<informalexample>
<screen>
-$ svn cat -r 1 concept/IDEA at BASEs
+$ svn cat -r 1 concept/IDEA at BASE
svn: E195012: Unable to find repository location for 'concept/IDEA' in
revision 1
</screen>
</informalexample>
@@ -724,7 +724,7 @@
<para>Subversion has no particular policy regarding the use of
properties. It asks only that you do not use property names that
- begin with the prefix <literal>svn:</literal>. That's the
+ begin with the prefix <literal>svn:</literal> as that's the
namespace that it sets aside for its own use. And Subversion
does, in fact, use properties—both the versioned and
unversioned variety. Certain versioned properties have special
@@ -2704,13 +2704,13 @@
<para>The original (Subversion 1.5) implementation of shallow
checkouts was good, but didn't support de-telescoping of working
- copy items. Subversion 1.6 remedies this problem. For example,
+ copy items. Subversion 1.6 remedied this problem. For example,
running <userinput>svn update --set-depth empty</userinput> in
an infinite-depth working copy will discard everything but the
topmost directory.<footnote><para>Safely, of course. As in
other situations, Subversion will leave on disk any files you've
modified or which aren't versioned.</para></footnote> Subversion
- 1.6 also introduces another supported value for
+ 1.6 also introduced another supported value for
the <option>--set-depth</option>
option: <literal>exclude</literal>. Using <option>--set-depth
exclude</option> with <command>svn update</command> will cause
@@ -2750,8 +2750,8 @@
you won't receive those when you update your working
copy.</para>
- <para>With Subversion 1.6, you could take a different approach.
- First, you'd check out the directory in full. Then you would
+ <para>Beginning with Subversion 1.6, you can take a different
+ approach. First, check out the directory in full. Then
run <userinput>svn update --set-depth exclude</userinput> on the
one subdirectory you don't care about.</para>
@@ -3035,7 +3035,9 @@
$ svn info banana.jpg
Path: banana.jpg
Name: banana.jpg
+Working Copy Root Path: /home/harry/project
URL: http://svn.example.com/repos/project/banana.jpg
+Repository Root: http://svn.example.com/repos/project
Repository UUID: edb2f264-5ef2-0310-a47a-87b0ce17a8ec
Revision: 2198
Node Kind: file
@@ -3201,10 +3203,11 @@
<informalexample>
<screen>
-$ svn info http://svn.example.com/repos/project/raisin.jpg
+$ svn info ^/raisin.jpg
Path: raisin.jpg
Name: raisin.jpg
URL: http://svn.example.com/repos/project/raisin.jpg
+Repository Root: http://svn.example.com/repos/project
Repository UUID: edb2f264-5ef2-0310-a47a-87b0ce17a8ec
Revision: 105
Node Kind: file
@@ -3790,8 +3793,8 @@
</screen>
</informalexample>
- <para>Subversion 1.6 brings two more improvements to externals
- definitions. First, it adds a quoting and escape mechanism to
+ <para>Subversion 1.6 brought two more improvements to externals
+ definitions. First, it added a quoting and escape mechanism to
the syntax so that the path of the external working copy may
contain whitespace. This was previously problematic, of course,
because whitespace is used to delimit the fields in an externals
@@ -3812,7 +3815,7 @@
</screen>
</informalexample>
- <para>Subversion 1.6 also introduces support for external
+ <para>Subversion 1.6 also introduced support for external
definitions for files. <firstterm>File externals</firstterm>
are configured just like externals for directories and appear as
a versioned file in the working copy.</para>
More information about the svnbook-dev
mailing list