Disable backing out merges?

[Dan Villiom Podlaski Christiansen]

On 7 Oct 2011, at 08:30, Angel Ezquerra wrote:

> Maybe what we need is not a way to fix a broken merge but a way to
> tell users and mercurial that they should not _use_ that broken merge?

I suppose you could achieve this via closing the line of development following the merge, and then add a hook which prevented adding new changesets that derive from such a line. Unless, perhaps, such changesets contain a magic string — “reopens X” or something similar. You'd probably want to add a bit of bookkeeping to prevent it from being slow, so it might make better sense as an extension.

It seems to me that, longer term, this is what the ‘liquid’ concept intends to deal with.

--

Dan Villiom Podlaski Christiansen
danchr at gmail.com