Mercurial > hgbook
diff en/ch01-tour-basic.xml @ 775:29f0f79cf614
Update paragraph IDs
author | Bryan O'Sullivan <bos@serpentine.com> |
---|---|
date | Thu, 16 Apr 2009 23:46:45 -0700 |
parents | 3b640272a966 |
children | c8d662d3cb40 |
line wrap: on
line diff
--- a/en/ch01-tour-basic.xml Thu Apr 16 23:45:07 2009 -0700 +++ b/en/ch01-tour-basic.xml Thu Apr 16 23:46:45 2009 -0700 @@ -131,7 +131,7 @@ &interaction.tour.clone; - <para>One advantage of using <command role="hg-cmd">hg + <para id="x_67c">One advantage of using <command role="hg-cmd">hg clone</command> is that, as we can see above, it lets us clone repositories over the network. Another is that it remembers where we cloned from, which we'll find useful soon when we @@ -233,7 +233,7 @@ the text message that the creator of the changeset entered to describe the changeset.</para></listitem> <listitem> - <para>Some changesets, such as the first in the list above, + <para id="x_67d">Some changesets, such as the first in the list above, have a <literal>tag</literal> field. A tag is another way to identify a changeset, by giving it an easy-to-remember name. (The tag named <literal>tip</literal> is special: it @@ -364,7 +364,7 @@ &interaction.tour.log-vp; - <para>The <option role="hg-opt-log">-p</option> option is + <para id="x_67e">The <option role="hg-opt-log">-p</option> option is tremendously useful, so it's well worth remembering.</para> </sect2> @@ -410,7 +410,7 @@ role="hg-opt-log">--rev</option> arguments.</para> </listitem> <listitem> - <para>If you are using short options, you can save typing by + <para id="x_67f">If you are using short options, you can save typing by running them together. For example, the command <command role="hg-cmd">hg log -v -p -r 2</command> can be written as <command role="hg-cmd">hg log -vpr2</command>.</para> @@ -430,7 +430,7 @@ <note> <title>Option naming consistency</title> - <para>Almost always, Mercurial commands use consistent option + <para id="x_680">Almost always, Mercurial commands use consistent option names to refer to the same concepts. For instance, if a command deals with changesets, you'll always identify them with <option role="hg-opt-log">--rev</option> or <option @@ -454,7 +454,7 @@ locally, we can just clone that instead. This is much faster than cloning over the network, and cloning a local repository uses less disk space in most cases, too<footnote> - <para>The saving of space arises when source and destination + <para id="x_681">The saving of space arises when source and destination repositories are on the same filesystem, in which case Mercurial will use hardlinks to do copy-on-write sharing of its internal metadata. If that explanation meant nothing to @@ -479,7 +479,7 @@ &interaction.tour.cat1; - <para>Let's edit this file so that it prints a second line of + <para id="x_682">Let's edit this file so that it prints a second line of output.</para> &interaction.tour.cat2; @@ -516,7 +516,7 @@ <tip> <title>Understanding patches</title> - <para>Remember to take a look at <xref + <para id="x_683">Remember to take a look at <xref linkend="sec:mq:patch"/> if you don't know how to read output above.</para> </tip> @@ -726,7 +726,7 @@ repository as the <emphasis>tip revision</emphasis>, or simply the <emphasis>tip</emphasis>.</para> - <para>By the way, the <command role="hg-cmd">hg tip</command> + <para id="x_684">By the way, the <command role="hg-cmd">hg tip</command> command accepts many of the same options as <command role="hg-cmd">hg log</command>, so <option role="hg-opt-global">-v</option> above indicates <quote>be