What do you do with MQ?

[Sam Steingold]

> * Martin Geisler <zt at nentbfg.pbz> [2011-12-13 18:25:42 +0100]:
>
> 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.
>
> Infact, when you start using mq like this, I feel it's very likely that
> you'll start having several such stashed commits around as separate
> patches and so you need to keep the patches.

see, you do no like the instructions above, so you would clearly be upset
if I were to copy they verbatim into the documentation.

>> now, could someone PLEASE put these incantations in both
>>
>> -- http://mercurial.selenic.com/wiki/GitConcepts
>> -- http://mercurial.selenic.com/wiki/MqExtension
>
> It is a wiki, so you're free to edit it yourself. You'll be asked to
> create an account if you don't already have one.

you are the mercurial expert, not me.
how can you expect me to write a good manual?!

the whole point of my request is that I want someone knowledgeable to
put the summary of this discussion into a more permanent and easily
locatable place.  this is not a matter of access.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://truepeace.org http://www.memritv.org http://jihadwatch.org
http://memri.org http://dhimmi.com http://mideasttruth.com http://ffii.org
Good: you CAN configure everything. Bad: you WILL configure everything.