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

Dan Villiom Podlaski Christiansen danchr at gmail.com
Thu Mar 4 15:46:14 CST 2010


On 4 Mar 2010, at 13:30, Dirkjan Ochtman wrote:

> On Thu, Mar 4, 2010 at 13:05, Dan Villiom Podlaski Christiansen
> <danchr at gmail.com> wrote:
>> # 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)::
> 
> I'd prefer to name only init -Q here.

Any particular reason? In my opinion, the commands -Q is most likely to be used for are ‘push’ and ‘pull’ and ‘commit’. For example, if you create a versioned patch queue on Bitbucket you needn't even do an ‘init -Q’.

> (In fact, maybe we should deprecate qinit?)

Good point. Perhaps we should deprecate qcommit too, while at it?

--

Dan Villiom Podlaski Christiansen
danchr at gmail.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1943 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100304/93bb03bc/attachment.bin>


More information about the Mercurial-devel mailing list