[svnbook] r3804 committed - * src/en/book/ch03-advanced-topics.xml...
svnbook at googlecode.com
svnbook at googlecode.com
Fri Oct 15 12:53:00 CDT 2010
Revision: 3804
Author: cmpilato at gmail.com
Date: Fri Oct 15 10:52:07 2010
Log: * src/en/book/ch03-advanced-topics.xml
* src/en/book/ch04-branching-and-merging.xml
Fix issue 43 by using a simple hyphen (-) instead of the −
character entity. While here, mark some text as <replaceable>.
http://code.google.com/p/svnbook/source/detail?r=3804
Modified:
/trunk/src/en/book/ch03-advanced-topics.xml
/trunk/src/en/book/ch04-branching-and-merging.xml
=======================================
--- /trunk/src/en/book/ch03-advanced-topics.xml Fri Oct 15 08:47:24 2010
+++ /trunk/src/en/book/ch03-advanced-topics.xml Fri Oct 15 10:52:07 2010
@@ -150,7 +150,7 @@
<para>The revision immediately <emphasis>before</emphasis>
the last revision in which an item changed.
Technically, this boils down to
- <literal>COMMITTED</literal>−1.</para>
+ <literal>COMMITTED</literal>-1.</para>
</listitem>
</varlistentry>
=======================================
--- /trunk/src/en/book/ch04-branching-and-merging.xml Thu Oct 14 09:13:08
2010
+++ /trunk/src/en/book/ch04-branching-and-merging.xml Fri Oct 15 10:52:07
2010
@@ -494,15 +494,18 @@
structure, or tweaks to metadata. In more common speak, a
changeset is just a patch with a name you can refer to.</para>
- <para>In Subversion, a global revision number N names a tree in
- the repository: it's the way the repository looked after the
- Nth commit. It's also the name of an implicit changeset: if
- you compare tree N with tree N−1, you can derive the exact
+ <para>In Subversion, a global revision
+ number <replaceable>N</replaceable> names a tree in the
+ repository: it's the way the repository looked after the
+ <replaceable>N</replaceable>th commit. It's also the name of
+ an implicit changeset: if you compare
+ tree <replaceable>N</replaceable> with
+ tree <replaceable>N</replaceable>-1, you can derive the exact
patch that was committed. For this reason, it's easy to think
- of revision N as not just a tree, but a changeset as well. If
- you use an issue tracker to manage bugs, you can use the
- revision numbers to refer to particular patches that fix
- bugs—for example,
+ of revision <replaceable>N</replaceable> as not just a tree,
+ but a changeset as well. If you use an issue tracker to
+ manage bugs, you can use the revision numbers to refer to
+ particular patches that fix bugs—for example,
<quote>this issue was fixed by r9238.</quote> Somebody
can then run <userinput>svn log -r 9238</userinput> to read about
the exact changeset that fixed the bug, and run
More information about the svnbook-dev
mailing list