[PATCH 1 of 2 STABLE] mq: mention the -Q/--queue option in the extension documentation

[Dan Villiom Podlaski Christiansen]

# HG changeset patch
# User Dan Villiom Podlaski Christiansen <danchr at gmail.com>
# Date 1267703834 -3600
# Node ID 9030c681ed0774216d3f80b7f3e4ce87c9ca69cd
# Parent  1694d2b0e58b0e25d53bad25cd0ff817d6841e2b
mq: mention the -Q/--queue option in the extension documentation.

diff --git a/hgext/mq.py b/hgext/mq.py
--- a/hgext/mq.py
+++ b/hgext/mq.py
@@ -14,6 +14,12 @@ applied patches (subset of known patches
 Known patches are represented as patch files in the .hg/patches
 directory. Applied patches are both patch files and changesets.
 
+A versioned repository for the patch queue can be created by using the
+-c/--create-repo option for 'qinit', or by using the "qclone"
+command. Passing the -Q/--queue option to one one of the normal
+repository commands, e.g. "update", "push" or "pull", causes them to
+work on the queue repository.
+
 Common tasks (use "hg help command" for more details)::
 
   prepare repository to work with patches   qinit
diff --git a/tests/test-mq.out b/tests/test-mq.out
--- a/tests/test-mq.out
+++ b/tests/test-mq.out
@@ -8,6 +8,11 @@ patches (subset of known patches).
 Known patches are represented as patch files in the .hg/patches directory.
 Applied patches are both patch files and changesets.
 
+A versioned repository for the patch queue can be created by using the -c
+/--create-repo option for 'qinit', or by using the "qclone" command. Passing
+the -Q/--queue option to one one of the normal repository commands, e.g.
+"update", "push" or "pull", causes them to work on the queue repository.
+
 Common tasks (use "hg help command" for more details):
 
   prepare repository to work with patches   qinit