[PATCH] add support for marking changesets as dead

[Martin Geisler]

Augie Fackler <durin42 at gmail.com> writes:

> On Feb 1, 2011, at 4:21 AM, Martin Geisler wrote:
>
>> Also, with pushkey, how will we solve the problem of cancelleing the
>> kill orders? If I pull from A and get meta data that says "kill X",
>> and if this is cancelled at A, then how do I know if I should push
>> the kill order back to A or if I should delete my own?
>
> You'd use pushkey to resurrect the head by deleting the dead marker
> via pushkey.

But if the dead marker is deleted in my clone to resurrect the changese,
then how do I know that I should not pull the dead marker again from a
remote repository?

With changesets, there is no question: I resurrect a changeset by
committing new live changesets along a different path.

-- 
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-devel/attachments/20110201/5b83e8d3/attachment.pgp>