MQ usability

Dan Villiom Podlaski Christiansen danchr at
Mon Aug 10 11:43:19 CDT 2009

On 10/08/2009, at 18.25, Dirkjan Ochtman wrote:

> 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:
> - remove qgoto, qnext, qprev, qtop: this functionality is already
> covered quite well by qpop, qpush, qseries and log.

It seems to me that the behaviour of ‘qseries’ would need to be  
changed first. Perhaps the default output could be what -v/--verbose  
currently does, and -q/--quiet be current normal output? It might also  
improve usability to have summaries shown by default.

> - possibly remove qsave/qrestore as well, since no one seems to use
> them (and many people get confused by 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.
> - add a qsplit command to deal with the actual usage of qrefresh for
> excluding hunks (interactive mode for this would rock even more).

I second all of these :)

> 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).

Perhaps ‘qnew’ should work like ‘commit’? That is, when no files are  
listed, all changes in the working copy will be used.

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

That'd be great!


Dan Villiom Podlaski Christiansen
danchr at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1943 bytes
Desc: not available
Url : 

More information about the Mercurial-devel mailing list