obliterate functionality?

Matt Mackall mpm at selenic.com
Tue Mar 18 16:41:56 CDT 2008

On Tue, 2008-03-18 at 14:35 -0400, cowwoc wrote:
> 1) Parent node may obliterate on its own code, when you pull changes 
> from it you're forced to accept their obliterate (since they own that code).

So, for instance, if you were writing a Mercurial feature in your branch
I thought was completely stupid (let's call it "burninate") but other
people liked, I could pull your branch, obliterate your burninate work,
and then suddenly everyone who pulls from me (including you) would have
their burninate work permanently erased from their local history? That
sounds very interesting!

Of course, you can't actually implement step 1 in a way that isn't
trivially circumvented. For instance, you could maintain your branch in
git. But now we're getting very silly..

Mathematics is the supreme nostalgia of our time.

More information about the Mercurial mailing list