Multiple Bookmark on merged changeset are converged

[Abderrahim Kitouni]

Hi,

2009/9/8 Shridhar Daithankar <ghodechhap at ghodechhap.net>:
> Hello,
>
> I was toying with bookmark and see how it fits with branching/tagging model
> that I am comfortable with.
>
> It is almost perfect(not syncing between repos aside) except how bookmarks are
> handled at merges.
>[...]
> --------------------
> You will notice that the bookmark moves along with your commit. With the
> extension set to track the "current" bookmark, only the one currently set will

This is the thing, the extension should be configured to tack the
"current" bookmarks, this can be done by adding

[bookmarks]
track.current = True

to your hgrc. It is in the extension help, but it's currently shadowed
because the command has the same name as the extension.

> move forward. This means that you can set two bookmarks to the same revision,
> and as long as you update appropriately only one will move forward. This is
> different from how the bookmarks extension operates by default, which entails
> all bookmarks moving forward when a commit is done on their parent.
> --------------------
>
> So this used to work and is a regression?
>
> Also any idea when the bookmarks will be integrated with push/pull? :) That
> would really be awesome.
>

I don't know.

HTH,
Abderrahim