[PATCH RFC] mq: add --fill option to qqueue command

Patrick Mézard patrick at mezard.eu
Thu May 3 05:32:51 CDT 2012


Le 03/05/12 12:00, Takumi IINO a écrit :
>> Please explain: What is this new "fill" concept? What problem does it solve
>> and how is it used?
> 
> I'm sorry.
> 
> New fill option concept is to have a function of the branch/branches command.
> I use patch queues like branches. I have multiple patch queues per repository.
> In that case, not empty (work in progress) patch queue is important.
> 
> Following table is a correspondence table.
> 
> branch                 |queue
> -----------------------+----------------------------------
> hb branch              |hg qqueue --active
> hg branch BRANCH_NAME  |hg qqueue --create QUEUE_NAME
> hg branbhes            |hg qqueue --list
> hg branches --active   |N/A (new option, hg qqueue --fill)
> hg branches --closed   |N/A
> 
> When fill option is added, do not have to look at the .hg directory.

Because you use long-living queues like long-living named branches. While I can see value in long-living branches, I do not see much in long-living queues. Cannot you create a new queue per feature and delete/purge it when it become empty? I am using qqueue too, I have "active" queues which contain stuff I am actively working on and I have "inactive" queues which contain random ideas or things I cannot work on immediately (because we are in code-freeze for instance). Note that none of these queues are empty, I delete queues becoming empty, so your command would not help me much.

What would help a bit is a kind of tagging system, but honestly using a (ridiculous) naming scheme like "inactive dead queues are prefixed with 'z-', inactive frozen queues are prefixed with 'zf-', etc. has been good enough for me.

--
Patrick Mézard


More information about the Mercurial-devel mailing list