[svnbook commit] r2599 - trunk/src/en/book
cmpilato
noreply at red-bean.com
Wed Jan 3 15:06:40 CST 2007
Author: cmpilato
Date: Wed Jan 3 15:06:40 2007
New Revision: 2599
Modified:
trunk/src/en/book/ch-advanced-topics.xml
Log:
* src/en/book/ch-advanced-topics.xml
(Peg and Operative Revisions): s/ampersand/at sign/ (a brain-o I seem to
repeatedly make).
Modified: trunk/src/en/book/ch-advanced-topics.xml
==============================================================================
--- trunk/src/en/book/ch-advanced-topics.xml (original)
+++ trunk/src/en/book/ch-advanced-topics.xml Wed Jan 3 15:06:40 2007
@@ -246,18 +246,18 @@
<para>The perceptive reader is probably wondering at this point if
the peg revision syntax causes problems for working copy paths
- or URLs that actually have ampersand characters in them. After
+ or URLs that actually have at signs in them. After
all, how does <command>svn</command> know whether
<literal>news at 11</literal> is the name of a directory in my
tree, or just a syntax for <quote>revision 11 of
<filename>news</filename></quote>? Thankfully, while
<command>svn</command> will always assume the latter, there is a
- trivial workaround. You need only append an ampersand to the
+ trivial workaround. You need only append an at sign to the
end of the path, such as <literal>news at 11@</literal>.
- <command>svn</command> only cares about the last ampersand in
+ <command>svn</command> only cares about the last at sign in
the argument, and it is not considered illegal to omit a literal
- peg revision specifier after that ampersand. This workaround
- even applies to paths that end in an ampersand—you would
+ peg revision specifier after that at sign. This workaround
+ even applies to paths that end in an at sign—you would
use <literal>filename@@</literal> to talk about a file named
<filename>filename@</filename>.</para>
More information about the svnbook-dev
mailing list