Distributed transaction rollback

[François Gannaz]

Le 2010-07-05, Dmitry Nezhevenko <dion at inhex.net> a écrit :
> Hi,
> 
> As everybody now, it's possible to rollback pushed revisions only if
> we've a way to notify everybody to reclone their repos.
> 
> I've some idea, related to 1.6 release. Now mercurial has a way to share
> some information between clones that is not a part of history (pushkey). 
> 
> What do you think about using this feature to share list of "rolled back"
> revisions? Some extension will verify that and automatically strip
> revisions in local history that are listed in such key.
> 
> There are still a few issues, like there should be a way to automerge list
> of rolled back revisions on push/pull.
> 
> Any ideas/suggestions? I'll try to implement something this weekend.
> 

Suppose I push a changeset with a new file, and A modifies this file. Now
if I rollback this and "push that rollback", what will your extension do
for A? Remove the local nodes if they are children of the deleted node? You'll
have to merge.

Apart from the above problem, I don't like the idea that an extension could
mangle my local history on the next pull. For instance, I like using my
changesets numbers.

I like the current policy:
* only modify your history if you haven't pushed anything
* rollback the last change
* histedit farther, at your own risk
* if you pushed it, or want to keep track or the revision, backout.

--
François