gup/gdown: properly mark these commands as deprecated They are no longer displayed in the documentation.

Backed out changeset 1b4c92621e23 This got published by mistake.

doc: integrate graphviz graphs in tutorials Use the mercurial-graphviz extension (https://bitbucket.org/octobus/mercurial_graphviz) in tutorials in order to have some dot graphs in the tutorials .t files. In order to run the tests, export the GRAPHVIZ_EXTENSION variable which points to your copy of the extension. Please be aware that pygraphviz should be installed in your environment. That should be sufficient for generating dot graphs in text format. Then generate the doc as usual, the sphinx-graphviz extension (http://www .sphinx-doc.org/en/stable/ext/graphviz.html) has been added and it should handle the generation of the graphs. Please be aware that you need the dot binary installed in your system. Please refer to the extension documentation for more configuration.

amend: lift the --interactive constraint on `--extract` The uncommit logic now supports interactive selection.

readme: mention the topic output cleanup

readme: mention the new --interactive mode for uncommit

uncommit: minor comment cleanup in the test Fix some of the sectionning and fix on comments.

uncommit: small cleanup of the interactive test setup

tests: add tests for interactively uncommitting by mentioning files

uncommit: fix the dirstate handling in `uncommit -i` This patch fixes the dirstate handling after `hg uncommit --interactive`. This patch is bit verbose about the logic and efforts are not put to plug the logic into existing logic as it's easier to understand like this. Plugging this into non-interactive logic deserves a separate patch.

uncommit: pre-indent a block in if-True The block will be moved in if-else in next patch.

uncommit: add an interactive option to uncommit This patchs adds an interactive flag to uncommit command which lets you choose hunks interactively. The implementation is as follows: 1) prompt user to select hunks to uncommit interactively 2) make a temporary commit of the hunks user selected 3) calculate the diff of temporary commit and changeset to be uncommitted 4) commit that diff which results in the changeset which should be there after uncommiting 5) create obsmarkers as required, phases and bookmarks handling 6) reroute the working directory

uncommit: pre-indent a block in if-True for the next patch

topic: provide more information when behind count cannot be computed The behind count has been confusing for various user and the associated error message is even worth. We try to clarify it to see if that helps.

topic: show the t0 even if topic is not yet touched