changeset 101:321732566ac1

A few bits of terminological clarification.

--- a/en/tour-basic.tex	Wed Oct 18 12:06:56 2006 -0700
+++ b/en/tour-basic.tex	Wed Oct 18 14:11:51 2006 -0700
@@ -491,6 +491,13 @@
 To find out what revision the working directory is at, use the
 \hgcmd{parents} command.
 \interaction{tour.parents}
+If you look back at figure~\ref{fig:tour-basic:history}, you'll see
+arrows connecting each changeset.  The node that the arrow leads
+\emph{from} in each case is a parent, and the node that the arrow
+leads \emph{to} is its child.  The working directory has a parent in
+just the same way; this is the changeset that the working directory
+currently contains.
+
 To update the working directory to a particular revision, give a
 revision number or changeset~ID to the \hgcmd{update} command.
 \interaction{tour.older}

--- a/en/tour-merge-merge.svg	Wed Oct 18 12:06:56 2006 -0700
+++ b/en/tour-merge-merge.svg	Wed Oct 18 14:11:51 2006 -0700
@@ -13,8 +13,7 @@
    id="svg2"
    sodipodi:version="0.32"
    inkscape:version="0.44.1"
-   sodipodi:docname="tour-merge-merge.svg"
-   sodipodi:docbase="/home/bos/hg/hgbook/en">
+   sodipodi:docname="tour-merge-merge.svg">
   <defs
      id="defs4">
     <marker

--- a/en/tour-merge.tex	Wed Oct 18 12:06:56 2006 -0700
+++ b/en/tour-merge.tex	Wed Oct 18 14:11:51 2006 -0700
@@ -96,6 +96,11 @@
 our former heads as its parents.  These are the same revisions that
 were previously displayed by \hgcmd{parents}.
 \interaction{tour.merge.tip}
+In figure~\ref{fig:tour-merge:merge}, you can see a representation of
+what happens to the working directory during the merge, and how this
+affects the repository when the commit happens.  During the merge, the
+working directory has two parent changesets, and these become the
+parents of the new changeset.
 
 %%% Local Variables: 
 %%% mode: latex