[PATCH] mq: introduce the qunmanage command

[Peter Arrenbrecht]

On Wed, May 28, 2008 at 3:36 PM, Jason Orendorff
<jason.orendorff at gmail.com> wrote:
> On Wed, May 28, 2008 at 5:35 AM, Christian Boos <cboos at neuf.fr> wrote:
>> One can question which of the two, a MQ managed patch or a regular
>> changeset, is the "higher ranked" object. From a MQ centric p.o.v, it's
>> certainly a MQ patch. So by looking at the name of the command only, I
>> would expect that with 'qpromote', MQ will promote a changeset to a
>> patch... but in your idea it's the reverse, so I'm not sure the name
>> helps to clarify what is going on.
>
> I don't know that anyone has explicitly stated the problem we're
> trying to solve here...
>
> 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.
>
> "qpromote" is an excellent name for this action, for the person in
> this circumstance, the person we're trying to help.  "qfinish" is good
> too.  But I have trouble imagining this user making the connection
> between "qunmanage" and the task at hand.  "manage" is a boring,
> almost meaningless word in English; it suggests "administrivia".  I
> think users would tend to skip past "qmanage" when looking at the list
> of commands, and "qunmanage" would look even less important.
>
> 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!"

+1 for qfinish. We might also want to mention qfinish (or whatever) in
the error message returned by push when patches are applied.
-parren