Gilles Moris <gill...@free.fr> writes:

I think it would -- when I told people that they cannot really get rid of their abandoned changesets, they asked me if they should then close the branch (they meant topological branch). I had to answer something like "well, yeah... that would work if it was a *named* branch...".

I still see some interesting uses for the idea of excluding some changesets from push/pull: Now that people are mad about 'hg qdelete' actually deleting stuff, then it would be nice to simply leave the changesets behind but mark them as dead so that they wont be pushed.

The same tool would allow us to implement 'hg commit --ammend' by marking the current tip as dead and making a new commit that incorporates the changes along with the changes in the old tip. Like this:

hg diff > tmp hg revert --all hg commit --mark-dead -m 'Killed by commit --ammend.' hg update -r -3 hg export -r -2 | hg import --no-commit - hg import --no-commit tmp rm tmp

where I assumed that things are nicely linear so that -3 and -2 refer to the parent and grandparent changesets.

Fast and powerful revision control: http://mercurial.selenic.com/