MQ usability

[Sebastien Douche]

On Mon, Aug 10, 2009 at 18:25, Dirkjan Ochtman<dirkjan at ochtman.nl> 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.

good idea :)

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

+1

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

+1

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

-1 if it's the default behavior.

> Any thoughts?

a basic command backup/restore the patchs stack?




-- 
Sebastien Douche <sdouche at gmail.com>
Twitter: http://bit.ly/afkrK (agile, python, open source)