1.1 --- a/en/mq.tex	Tue Jun 27 23:21:05 2006 -0700
     1.2 +++ b/en/mq.tex	Thu Jun 29 00:32:35 2006 -0700
     1.3 @@ -263,8 +263,8 @@
     1.4  \subsection{Manipulating the patch stack}
     1.5  
     1.6  The previous discussion implied that there must be a difference
     1.7 -between ``known'' and ``applied'' patches, and there is.  MQ can know
     1.8 -about a patch without it being applied in the repository.
     1.9 +between ``known'' and ``applied'' patches, and there is.  MQ can
    1.10 +manage a patch without it being applied in the repository.
    1.11  
    1.12  An \emph{applied} patch has a corresponding changeset in the
    1.13  repository, and the effects of the patch and changeset are visible in
    1.14 @@ -287,6 +287,13 @@
    1.15  or two patches, the output of \hgcmd{qseries} remains the same, while
    1.16  that of \hgcmd{qapplied} has changed.
    1.17  
    1.18 +\begin{figure}
    1.19 +  \centering
    1.20 +  \grafix{mq-stack}
    1.21 +  \caption{Applied and unapplied patches in the MQ patch stack}
    1.22 +  \label{fig:mq:stack}
    1.23 +\end{figure}
    1.24 +
    1.25  MQ does not limit you to pushing or popping one patch.  You can have
    1.26  no patches, all of them, or any number in between applied at some
    1.27  point in time.