bookmarks features

[Greg Ward]

On Thu, Aug 26, 2010 at 5:20 PM, Chad Dombrova <chadrik at gmail.com> wrote:
> i'm planning on implementing some bookmark features that i need at my
> workplace, but i thought i'd post the ideas here to see if they could be
> improved or would be useful for integration into mercurial.  i've tried to
> design them to be fairly generic and hopefully generally useful:
>
> Bookmark Namespaces
> ===================
> use namespaces to avoid name clashes when pushing and pulling, and to inform
> of a bookmark's source.
> [bookmarks]
> default-remote-namespace = remote
> use-remote-namespaces = true
> if ``bookmarks.use-remote-namespaces`` is enabled, when pulling bookmarks
> the first name given to the remote path in [paths] (excluding default and
> default-push) will be used for the namespace, otherwise
> ``bookmarks.default-remote-namespace`` will be used.
> the namespace separator defaults to '|' but can also be specified using
> ``bookmarks.namespace-sep``

There are many nice things about git, and there are many things about
git that annoy me.  I think the one that annoys me most is the whole
business about "origin/" and "remote" branches and all that cruft.

But if you *are* going to reimplement that (mis)feature, you might as
well use the same separator: "/".

(Or have I totally misunderstood this feature?)

> Shared Bookmarks
> ================
> allows shared repositories to use a single shared set of bookmarks.
> configure by setting::
> [bookmarks]
> shared = true
> shared repositories with ``bookmarks.shared`` enabled use the bookmarks

Sounds useful.  We don't use bookmarks, but we make heavy use of
shared repos.  I bet if we did use bookmarks we would want this
feature pretty soon.

Greg