diff en/mq.tex @ 11:e9d5b4c3d16b

First SVG image!
author Bryan O'Sullivan <bos@serpentine.com>
date Thu, 29 Jun 2006 00:32:35 -0700
parents a25335b56825
children 1f692024d438
line wrap: on
line diff
--- a/en/mq.tex	Wed Jun 28 20:29:21 2006 -0700
+++ b/en/mq.tex	Thu Jun 29 00:32:35 2006 -0700
@@ -263,8 +263,8 @@
 \subsection{Manipulating the patch stack}
 
 The previous discussion implied that there must be a difference
-between ``known'' and ``applied'' patches, and there is.  MQ can know
-about a patch without it being applied in the repository.
+between ``known'' and ``applied'' patches, and there is.  MQ can
+manage a patch without it being applied in the repository.
 
 An \emph{applied} patch has a corresponding changeset in the
 repository, and the effects of the patch and changeset are visible in
@@ -287,6 +287,13 @@
 or two patches, the output of \hgcmd{qseries} remains the same, while
 that of \hgcmd{qapplied} has changed.
 
+\begin{figure}
+  \centering
+  \grafix{mq-stack}
+  \caption{Applied and unapplied patches in the MQ patch stack}
+  \label{fig:mq:stack}
+\end{figure}
+
 MQ does not limit you to pushing or popping one patch.  You can have
 no patches, all of them, or any number in between applied at some
 point in time.