# HG changeset patch
# User Steve Borho <steve@borho.org>
# Date 1256701609 18000
# Node ID 102f89d20be133b8b0e9ff3596156149db00cc0f
# Parent  9ba99e6dc2555d74d121308673be2a5750eb9cf9
remove spurious 'hg' from mq command line options

diff -r 9ba99e6dc255 -r 102f89d20be1 en/ch12-mq.xml
--- a/en/ch12-mq.xml	Sun Oct 18 22:55:10 2009 -0700
+++ b/en/ch12-mq.xml	Tue Oct 27 22:46:49 2009 -0500
@@ -438,7 +438,7 @@
 	<command role="hg-ext-mq">qpop</command> each operate on a
 	single patch at a time by default, you can push and pop many
 	patches in one go.  The <option
-	  role="hg-ext-mq-cmd-qpush-opt">hg -a</option> option to
+	  role="hg-ext-mq-cmd-qpush-opt">-a</option> option to
 	<command role="hg-ext-mq">qpush</command> causes it to push
 	all unapplied patches, while the <option
 	  role="hg-ext-mq-cmd-qpop-opt">-a</option> option to <command
@@ -469,10 +469,10 @@
 	named <option>-f</option>.  The exact meaning of
 	<option>-f</option> depends on the command.  For example,
 	<command role="hg-cmd">hg qnew <option
-	    role="hg-ext-mq-cmd-qnew-opt">hg -f</option></command>
+	    role="hg-ext-mq-cmd-qnew-opt">-f</option></command>
 	will incorporate any outstanding changes into the new patch it
 	creates, but <command role="hg-cmd">hg qpop <option
-	    role="hg-ext-mq-cmd-qpop-opt">hg -f</option></command>
+	    role="hg-ext-mq-cmd-qpop-opt">-f</option></command>
 	will revert modifications to any files affected by the patch
 	that it is popping.  Be sure to read the documentation for a
 	command's <option>-f</option> option before you use it!</para>
@@ -808,9 +808,9 @@
 
     <para id="x_404">On my old, slow laptop, I was able to <command
 	role="hg-cmd">hg qpush <option
-	  role="hg-ext-mq-cmd-qpush-opt">hg -a</option></command> all
+	  role="hg-ext-mq-cmd-qpush-opt">-a</option></command> all
       1,738 patches in 3.5 minutes, and <command role="hg-cmd">hg qpop
-	<option role="hg-ext-mq-cmd-qpop-opt">hg -a</option></command>
+	<option role="hg-ext-mq-cmd-qpop-opt">-a</option></command>
       them all in 30 seconds.  (On a newer laptop, the time to push
       all patches dropped to two minutes.)  I could <command
 	role="hg-ext-mq">qrefresh</command> one of the biggest patches
@@ -866,7 +866,7 @@
 	  -a</option></command> your patches, then <command
 	role="hg-cmd">hg pull</command> changes into the underlying
       repository, and finally <command role="hg-cmd">hg qpush <option
-	  role="hg-ext-mq-cmd-qpop-opt">hg -a</option></command> your
+	  role="hg-ext-mq-cmd-qpop-opt">-a</option></command> your
       patches again.  MQ will stop pushing any time it runs across a
       patch that fails to apply during conflicts, allowing you to fix
       your conflicts, <command role="hg-ext-mq">qrefresh</command> the
@@ -1138,9 +1138,9 @@
 	  update</command> changes to patches or the <filename
 	  role="special">series</filename> file, you will have to
 	<command role="hg-cmd">hg qpop <option
-	    role="hg-ext-mq-cmd-qpop-opt">hg -a</option></command> and
+	    role="hg-ext-mq-cmd-qpop-opt">-a</option></command> and
 	then <command role="hg-cmd">hg qpush <option
-	    role="hg-ext-mq-cmd-qpush-opt">hg -a</option></command> in
+	    role="hg-ext-mq-cmd-qpush-opt">-a</option></command> in
 	the underlying repository to see those changes show up there.
 	If you forget to do this, you can confuse MQ's idea of which
 	patches are applied.</para>