What do you do with MQ?

[Martin Geisler]

"Haszlakiewicz, Eric" <EHASZLA at transunion.com> writes:

>> -----Original Message-----
>> From: mercurial-bounces at selenic.com [mailto:mercurial-
>> 
>> Sam Steingold <sds at gnu.org> writes:
>> 
>> >> * Arne Babenhauserheide <near_ono at jro.qr> [2011-12-13 06:46:57 +0100]:
>> >> * shelve away changes, commit something else, get them back.
>> >>    hg qnew stash-work-in-progress; hg qpop
>> >>    hg qpush; hg qfinish tip; hg strip -k tip
>> 
>> I don't like the last line -- it feels quite unnatural to me to
>> finish a patch just to strip it. I've certainly never used mq like
>> that. Somehow, I feel that people that insist on getting the changes
>> "out" of mq have misunderstood it -- you can just keep the changes in
>> mq and work with them there.
>
> Except that you can't because important operations are missing. An
> example of one of the most basic things that you can't easily do:
>
>   hg stat
>
> Not being able to see what files I'm working with makes mq very
> difficult for me to work with.

I'll admit that this also puzzled me at the beginning until I realized
that applied mq patches are real changesets. I know Matt also wrote
this, but it's apparently new to a lot of people, so I think it's okay
to repeat this :)

So I have a crude alias that I use once in a while:

  [alias]
  qstatus = status --rev -2 --rev -1

(I should change to Matt's version, but this was from before revsets.)

Overall, I don't use this alias nearly as much as I thought I would.
Instead, I use the excellent mq integration in TortoiseHg to see what is
in my patch.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial/attachments/20111214/c9ebb208/attachment.pgp>