Merge default new feature in stable 0.3.0 planned

stabilize: clear error message than conflict during rebase offer no hope The warning is big and ugly. It will be removed when stab handle that properly.

doc: readme and uncommit reference

readme: explain "instalation process" if it may be called like that.

merge with stable doc update

setup: update alias with new wording

obsolete: add an hidden revset

obsolete: basic commit --amend support commit --amend still strip. but lay obsolete marker down anyway

evolve: add a prune alias for kill pro: - it's short - It's already used in version control context - it's in the same lexical field than `graft`

evolve: warn when uncommit leave an empty changeset This is intended to replace the proposed --delete flag.

evolve: improve kill testing show than uncommited changes are properly merged

oops (forget to amend)

uncommit: warn about new instability

uncommit: add --all option Convenient when combined with --exclude.

uncommit: handle bookmarks Extract the bookmarks handling code from amend and share it with uncommit.

evolve: add uncommit command

obsolete: enable rebase --keep again We still never strip anything. But using --keep on the command line dos not lay marker.

[obsolete] fix revset error message

evolve: warn when latecomer changeset are created

obsolete: detect late comer during push

obsolete: add latecomer computation and display

obsolete: add precursors and successors revset.

update revset vocabulary to use precursors, successors

obsolete: remove unused variable in rebase wrapping

evolve: tidy up a bit - long lines - extra blank lines - commands options descriptions

obsolete: make collapse create less markers Collapsing A and B into C was registering: A -> C B -> C A -> B At this point, the last relation brings nothing and is removed for the sake of simplicity: A -> C B -> C test-evolve.t is slightly modified as one of the relations let stabilize compute a target outside of the parent revision tree. This is a stabilize bug, not trivial to fix, so let's tweak the test for now.

obsolete: remove unused code from reposetup()

obsolete: suspended changeset with secret only children should be secret too test-obsolete-push.t: exhibit outgoing bug with suspended changeset in this case

obsolete: add 'obsolete' keyword The obsolete keyword displays the node status among 'stable', 'unstable', 'suspended', 'extinct'.

obsolete: unify collapsed revisions markers handling When collapsing A, B and C into D, amend was registering: A -> D B -> D A -> B C -> D A -> C while the rebase wrapper was doing: A -> D B -> D C -> D At this point, I have no argument to favor one or another or even a new one like: A -> B B -> C C -> D so I am aligning the rebase implementation on the older amend one. At least we can now change them all at once.