> On 4/18/23 22:10, Uwe Brauer wrote:
> Min is just going to give you the lowest revision number matching a
> revset. This is not what you want (and in this case, the revset only
> match one revision).
> Bookmark does not record this information, so you don't have a
> definitive answer here (this is part of why topic exists).
Right, but one observation, in the current implementation, once you push
to a publishing remote repository, the topic information is hidden.
So lately I have seen repositories which on purpose are configured to be
non-publishing, for example hg-git in order to still get the topics
displayed when you pulled
changeset: 1914:502212b50354
│ tag: tip
│ Remote_Branch:
https://foss.heptapod.net/mercurial/hg-git/default:drop-compat
│ Branch: default
│ Author: Dan Villiom Podlaski Christiansen <
dan...@gmail.com>
│ Date: Fri, 01 Apr 2022 18:56:00 +0200
│ Topic: drop-compat
│ Phase: draft
│ Summary: ci: drop compat for Mercurial 5.2
│
○ changeset: 1913:15c66b3006a8
│ Branch: default
│ Author: Dan Villiom Podlaski Christiansen <
dan...@gmail.com>
│ Date: Fri, 01 Apr 2022 16:26:09 +0200
│ Topic: drop-compat
│ Phase: draft
│ Summary: compat: drop support for Python 3.6
│
The downside of this approach is that you loose partially the power of
phases.
So would it be convenient to display, at least optionally, topics of
phases that are published? (I know I should ask this on the evolve
mailing list, but I am curious to hear what others on this list think
about it).
> If all your bookmark create a unique and independant topological
> branch you can use `roots(only("bookmark-name"))` to find the root of
> that unique topological branch.
Thanks! The point is as I said the bookmarks have their origin in a git
repository (but even in git it is not straightforward to find out where
a git branch starts!).
The roots command seems not to work in hg 5.2, so in which version was
it introduced?
regards