packagin: mark stable branch as 6.4.1.dev This help prevent confusion with installing intermediate version

topics: abort if user wants to show the stack of a non-existent topic

stack: show unstable state for the current revision if it is one (issue5553) Before this patch if the current revision is unstable, hg stack does not show the unstable state. This patch fixes that by showing both current and unstable state for the current revision if that's unstable.

topics: some minute fixes to the documentation which shows up in help I am not a native but these changes are simple and obvious.

topics: make sure we commit on new parents while changing topics (issue5441) While changing topics of a set of linear commits, we used to commit our new changesets with new topic on parents of its predecessor i.e. changeset before the topic change. If the topic of parent was also changed, that parent will become obsolete and hence resulting the cnew commit in unstable state. For a set of linear commits this repeats and we end up in a tree state as mentioned in the bug. This patch fixes the bug by checking whether the parent was obsoleted and if yes, commit on the new parent.

tests: add a test to show issue5441 in test-topic.t The issue will be fixed in the next patch and the test will be helpful to show that.

merge back with stable (test change from stable has been reverted)

Added tag 6.4.0 for changeset e60248f26f92

packaging: prepare version 6.4.0

readme: fix readme for future 6.4.0

test-compat: merge with mercurial-3.9

test-compat: merge with mercurial-4.0

test-compat: merge with mercurial-4.1

compat-test: merge with stable

test-compat: fix previous merge The merge was a bit too heavy handed in dropping some part of the test.

merge with default Integrate new development around obsfate.

obsfate: by default only display the username if differ from the current one This will will keep the output simple in the simple case.

obsfate: display more data about direct prune markers This does not handle all cases, but this should handle the most common ones.

obsfate: split markers fetch from successor set annotation This will help to improve support for pruned changesets.

obsfate: mark successorsetallmarkers public We are about to use it in another module.

obsfate: mark 'preparesuccessorset' as public It is used in another module so it is not really private.

obsfate: use 'split' as verb when appropriate

obsfate: improve prune support in _successorsetverb In the prune case, still have markers (at least the prune markers). If we want to be able to return these markers we need the underlying function to support it.

obsfate: rename 'successorsset' to 'sset' in the loop The old name make it too close to 'successorssets', and the shorter name is not ambiguous in the context anyway.

template: use hex node in the obsmarkers used in the obsfate template This was pointed by Yuya and yuya is right.

template: use hex successors in obsfate This was spotted by Yuya.

template: use hex-node in successors AS pointed by yuya on the list, the raw data for the template should be hex and not binary.

template: update successors doc I'm not very happy about it, but at lease there is a show description now