Proposal: "Save" version of Transplant

[Martin Geisler]

Daniel Carrera <dcarrera at gmail.com> writes:

> On Tue, Jul 13, 2010 at 10:39 AM, Martin Geisler <mg at aragost.com> wrote:
>> This is no different from using transplant -- you are storing
>> changset H as a (dumb) patch and then you apply it to changeset E. If
>> a file has been renamed inbetween H and E, then the qpush will fail
>> just like transplant fails.
>>
>> The whole idea of Daniel's recipe is to use the merge machinery to
>> track renames while cherry-picking.
>
> Yes, exactly. Someone understands me!
>
> I couldn't reply well to Bill because I didn't understand how his
> proposal worked. I don't know MQ. I just had the feeling that MQ is
> not what I'm looking for.

Yeah, in this case you're not looking for MQ, though it is a very nice
powertool :)

To describe it briefly: MQ lets you manage a stack of patches. The
patches are just textual descriptions of the changes, see 'hg export'.
The nice thing about patches is that they can be changed, and so you can
refine your patches until you are happy with them. The patches double as
changesets while you work with them, so they appear in 'hg log' and
other hg commands. When you are done with a patch, you finalize it,
thereby turning it into a normal, immutable changeset.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/