Counterintuitive tag behaviour (broken design?)

[Matt Mackall]

On Wed, Mar 14, 2007 at 09:44:18PM +0100, Christian Boos wrote:
> Matt Mackall wrote:
> >...
> >For a tag like "the-latest-build-that-actually-works", if this
> >happens, it's a don't-care. Tags on both branches are equally valid
> >unless one obsoletes the other. Using the most recently committed or
> >pulled version of the tag (aka tip-most) is -the right thing to do-.
> >  
> 
> Isn't there a branch locality argument worth taking into account here?
> E.g. if `hg branch` gives you 'stable', you're certainly more interested 
> in the latest "the-latest-build-that-actually-works" on the 'stable' 
> branch than in a more recent "the-latest-build-that-actually-works" on 
> an 'experimental' branch...

Maybe. Or maybe people should use tags like "latest-working-stable". I
would prefer tags to be global for simplicity.

(If you need a tag like that, your project has problems.)

-- 
Mathematics is the supreme nostalgia of our time.