[PATCH 2 of 2] mq: flag as deprecated

[Angel Ezquerra]

On Sat, Jun 7, 2014 at 9:54 PM, Augie Fackler <raf at durin42.com> wrote:
> # HG changeset patch
> # User Augie Fackler <raf at durin42.com>
> # Date 1398790621 14400
> #      Tue Apr 29 12:57:01 2014 -0400
> # Node ID 639a70111cffe127bbef74d219a4358323f52e1c
> # Parent  b78de345e00af1f2f2ca88b98eaafe2ae05824c2
> mq: flag as deprecated
>
> hg config --edit now directs users to 'hg help extensions' to learn
> more about extensions and see the available ones. Nearly everything
> that can be done with mq can be done better and more safely using
> rebase, histedit, and commit --amend. As such, hide mq from new users
> so they won't accidentally find the glass that's in our sandbox.

I know that this is something that must (and should!) eventually
happen, but IMHO from the perspective of the TortoiseHg users (those
that rarely if ever see the command line mercurial interface) I don't
think we are ready to deprecate mq.

The TortoiseHg history editing workflow is still very much mq-based.
TortoiseHg supports "commit --amend" but that does not fully match
what you can do with QRefresh (you cannot easily remove files from a
commit with "hg commit --amend", for example). I have not used
histedit much myself but it does not seem very "GUI friendly" (because
it is basically a really good text-based UI). We could possibly put
some GUI on top of it but since evolve is the future I guess it would
make more sense for us to improve our evolve support (and this is
something that we are hoping to do during the next sprint).

Of course TortoiseHg users are unlikely to see the a deprecation
message (unless mq is removed at some point from the mercurial
releases) so perhaps this is not a big deal anyway...

Cheers,

Angel