doc: make paragraphs before example code end with "::" for reST syntax This prevents lines in an example code from being treated as a part of normal paragraph. For issue example, lines are folded into one paragraph.

topic: centralize compatibility logic between hg versions into compat module This patch can delay loading obsutil and obsolete modules until they are actually used at "hg topics" or so, if demandimport of Mercurial is enabled.

readme: mention the improvement to stack in the readme

test: issue a clarifying graph print in tests/test-stack-branch.t

stack: properly order stack when gaps existing inside it We transitively search for the next "stack" ancestors, of changeset in the stack not based on other revision of the stack. This should help having a consistent display when topic are interleaved.

stack: display both parent with displaying merge This will help understanding merge in the stack. More test involving merge are adding in the next changeset.

tests: add tests for showing stack when merge is involved This patch adds tests of showing stack when merges are involved. This will help us in changing the behaviour and realising that in later patches.

stack: move data computation on the object We gather multiple data about the stack on the object. Let us move this on the object and keep it cached there.

stack: replace 'getstack' with direct call to 'stack' The dedicated function do not add any value. We can update all the callers.

stack: introduce a rich stack object The logic around stack object become more and more complex. We great and object to gather and abstract it.

tests: add tests for `hg stack` showing surprising behavior with gaps The test will help us to analyse in next commit if the things are fixed or not.

topic: check availability of obsutil.getmarkers() for portability Before this patch, topic extension causes unintentional failure with Mercurial earlier than 4.3, because obsutil.getmarkers() has been available since Mercurial 4.3 (tests for topic on mercurial-4.* branches fail, too). This breaks "minimumhgversion = '4.0'" declaration of topic extension. This patch fixes this issue in a straightforward way for simplicity on stable branch. I'm planning to centralize such portability logic in topic extension into topic/compat.py or so on default branch for efficiency at runtime, like as evolve/compat.py.

tests: add more explicit test about empty topic from publishing

convertbookmark: advertise the new command in the readme The command is in a good enough shape now.

convertbookmark: properly convert stacked bookmarks We ignores pure descendant when looking for revision to convert. This adds support for cases were a linear stack contains multiple bookmark (or un-bookmarked descendants exists). In this case, some changeset are left orphan, but we'll consider the issue as minor for now.

convertbookmark: perform all actions at the end This will make the whole operation more deterministic and robust.

converbookmark: split target computation from actual update This will allow for further refactoring helping consistency.

convertbookmark: extract the revset into a module level constant This will make it easier to read and modify the query.

convertbookmark: properly exclude public changeset Public changeset are immutable and cannot have a topic anyway.

test: add a new root changeset to all debugconvertbookmark test case We'll make this root changeset public to check the debugconvertbookmark logic in that regards. It is added in its own changeset since it massively impact all output.

tests: import section in 'test-topic-debugcb.t' We now have two levels of titles to clarify some aspect of the tests.

test: avoid using debugdrawdag in 'test-topic-debugcb.t' The 'debugdrawdag' utility adds local tags that prevent hidden changeset to get hidden. We will do without that extension for now.

tests: add more tests for debugconvertbookmark

convertbookmark: add logic to skip revisions with multiple bookmarks When a user tries to converts a bookmark to topic which is on a changeset with more bookmarks we skip that.

topics: add a new debugconvertbookmark command to convert bookmarks to topics This new command, aliased to debugcb converts bookmarks to topics. This command either accept name of a bookmark using flag '-b' or '--all'. If a bookmark is passed using '-b', the whole stack defined by that bookmark is converted to topics. If '--all' is passed, the above thing is repeated for every bookmark in the repository. If the revset which we are using unable to decides revisions of the stack and return an expty set, in that cases we are not deleting the bookmark as we are not writing any topics of the same name as that of bookmark. Also currently if a changeset has two bookmarks, than there is buggy behaviour. So these are known lackings in the current implementation which will be fixed in upcoming patches. This also adds tests for the same.

topic: support --rev argument and properly process then as user input Revisions inputed by the users should be processed using `scmutil.revrange`. This will take alias into account and allow extensions to monitor the user inputs. As a side effect, the '_changetopics' function takes revisions as argument. make the API clearer.

topic: move a status message in the right scope The finally get runs on failure so we should not advertise rewrite topic in the case. In addition the 'rewrote' variable can be undefined in the finally.

obsfate: use effect flag information for computing a better verb

compat: make it more clear that evolve need Mercurial >= minversion The message is more clear when mercurial isn't installed at all.

doc: record all the missings and strange bit we know We know the doc is not as fresh as it could be. We make sure the reader is aware too.

directaccess: fix with tree without order 1b28525e6698 removes order from tree, changing the indexes in gethashsymbols. Fix that

compat: adapt to test output changes different access pattern in 4.4 means different results. Make evolve works with mercurial core 72b5f4d53c58

compat: adapt to rebase change in coming 4.4 Make evolve works with mercurial core 72b5f4d53c58

topics: import lock as lockmods We'll need a 'lock' variable in the next changeset. we move the module out of the way ahead of time for clarity.

topics: make sure we have some restrictions on topic names This patch makes sure we don't allow topic names with just whitespaces, and other checks which we do for a bookmark.

topic: add test showing no restrictions on topic names Currently we don't have any restrictions on topic names and each of the topic name works. We want them to not work as some of them are used internally and only integers can be rev numbers too.

index: edit pass by native english speaker

topic: reword and simplify explanation of "behind"

topic: tutorial grammar fixes

doc-front-page: link to the changeset evolution section in the document The section is unlikely to be perfect, but at least it exists.

doc-front-page: use a clearer statement about the experimental status This text comes form the Mercurial wiki.

doc-front-pagE: add a paragraph about "why the extension" Let us clarify why there is an extension in the first place.

doc-front-page: expand the paragraph about changeset evolution We clarify the part of the explanation about the changeset evolution concept.

doc-front-page: rename the "next step" section This are pointer to relevant section in the doc. It is a bit double usage with the table of content. We at least clarify the title.

doc-front-page: mention that "Changeset Evolution" is a specific concept It will get it own paragraph soon.

doc-front-page: include the index in the TOC This will help important content to stand forward.

doc-front-page: add a title to the part about the extension We'll rework this section more in depth, but I would like it to have a title first to have it show up in the table of content.

doc-front-page: add a feature summary at the beginning of the page

doc-front-page: mention the mailing list in the documentation It is an important tool to keep people up to date.

doc-front-page: move installation instruction earliero This is important for user.

doc-front-page: move introduction before the table of content This should make a friendlier landing.

doc: simplify the reference to in-core features This should do the whole thing lighter.

doc: be less dramatic about changeset immutability Quoting Phillipe: "This is not a Tolkien Novel".

doc: clarify the introduction sentence

topics: allow use a --current when setting a topic This patch allow to use the current flag which can be used by user set existing revs to the current topic.

topic: make --clear + topicname invalid The two flags are mutually exclusive.

topics: add a current flag to display current topic This patch adds a current flag which can be used by user to display the current topic.

topics: add a missing trailing comma on list of flag This will make the next changeset easier to read.

doc: let mercurial find where evolve is installed

doc: use pip to install evolve

doc: reword "target repository" to "remote repository"

doc: typo fixes

doc: use "hidden" instead of "invisible"

tests: add whitespaces in test-topic.t to make it more readable