[PATCH] mq: introduce the qunmanage command

Dirkjan Ochtman dirkjan at ochtman.nl
Wed May 28 05:40:15 CDT 2008

On Wed, May 28, 2008 at 12:35 PM, 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.

MQ patches are transient, repository history (changesets) are
permanent. Therefore, the latter are "higher ranked". Seems intuitive

> I don't remember if that has been suggested before, but 'qrelease' might be
> another option: you stop editing a patch and transform it in regular
> immutable changeset, freezing it. That command would convey the traditional
> CM meaning of release ("A version of a piece of software which has been made
> public") but also the "release" of control after it has been acquired by
> 'qmanage'.

Yeah, it's been suggested, but I think the "release" word has too many
meanings to be very useful.



More information about the Mercurial-devel mailing list