MQ usability

Christian Ebert blacktrash at
Mon Aug 10 13:09:39 CDT 2009

* Dirkjan Ochtman on Monday, August 10, 2009 at 18:25:58 +0200
> So people invariably complain that MQ is hard to use. On the other
> hand, everyone recognizes that it's also quite powerful. I'd like to
> fix the former without losing the latter. Therefore, I have a few
> proposals to improve on the current situation:

There is an upside to mq's demanding usage: it entices me to
use/think about core commands first.

> - remove qgoto, qnext, qprev, qtop: this functionality is already
> covered quite well by qpop, qpush, qseries and log.

qgoto? How is this covered by the other commands?

> - possibly remove qsave/qrestore as well, since no one seems to use
> them (and many people get confused by them).

I don't, because I don't understand them. Not sure whether this
counts as argument for removing them ;-)

> - make qrefresh <file> not exclude other files from the patch: this
> trips a lot of people up, and the other behavior is often useful, too.

I don't understand. What is qrefresh <file> for, then? I often
get bitten from the other end: I do a qrefresh forgetting to
specify the file and suddenly have changes in the patch that I
did not want.

> - add a qsplit command to deal with the actual usage of qrefresh for
> excluding hunks (interactive mode for this would rock even more).

That's probably what I want then.

> Other possible niceties:
> - make qnew vs. qnew -f more intuitive somehow (I'm really not sure
> how, but this usage of -f doesn't really fit in).

Can't tell, I'm used to it now.

> - make qpush try a merge instead of throwing .rej files around


\black\trash movie    _C O W B O Y_  _C A N O E_  _C O M A_
                     Ein deutscher Western/A German Western


More information about the Mercurial-devel mailing list