[PATCH] mq: introduce the qunmanage command

Paul Moore p.f.moore at gmail.com
Wed May 28 09:30:33 CDT 2008

On 28/05/2008, Jason Orendorff <jason.orendorff at gmail.com> wrote:

> I don't know that anyone has explicitly stated the problem we're
> trying to solve here...

Good point

> A newish MQ user is done with a patch and wants to push it.  He
> doesn't know what command to use.  Note that this is one of a tiny
> handful of commands that people need in order to use MQ for basic
> everyday work (the others are qnew, qrefresh, qpush, and qpop).  Yet
> our user types "hg help", looks at the "q" commands, and sees nothing
> likely.

Hmm, my action at that point is usually

    hg email qbase:qtip


Seriously, what proportion of users use mq to play with stuff on their
own repositories and then commit? For personal use, I'd be happy with
normal commits. I use mq to develop a patch for sending to an external
project, where I want to produce a "cleaned up" version. So on that
basis, qpromote/qfinish or whatever isn't so much a "basic" command as
something somewhat more advanced.

> Any of qpromote, qfinish, or qrelease is fine with me.  I think for
> the specific person we're trying to help, "qfinish" does the best job
> of jumping out of "hg help", saying "pick me, pick me!"

This I do agree with, though. I'm still OK with qpromote, but qfinish
has the implication of "the last thing you do", which is the right


More information about the Mercurial-devel mailing list