[Monotone-devel] A question about tags

[Jack Lloyd]

Is it intentional / planned that tags in Monotone are database wide
rather than branch wide? By which I mean, if two projects

net.randombit.test1
net.randombit.test2

share a database, then tagging revisions in both of them as (say)
'1.0' will cause all kinds of annoying conflicts (ambiguous selector
expansions, etc)

This seems really bad/surprising to me... in particular because
Monotone requires a single database for servers... so two projects
that have no knowledge of each other and acting non-maliciously can
cause conflicts such that they can't both be reasonably used from the
same db.

Is this just an implementation artifact, or is it considered the Right
Thing to do?

When looking up a tag, should there be an implicit

b:<current workspace branch>*

To only search for matching tags in subbranches? I guess this doesn't
work when you are in a branch looking for a tag on mainline, etc ...
It almost feels like you want some notion of project-wideness, which
is hard now because branch names are basically free-form... argh.

-Jack