I know it's a pain but really, ideally, this is a bug. Either the system should cope with multiple identical tags, or it shouldn't allow you to make them. Principal of least astonishment.
I guess you would have to cope with them, since you can't know that you've currently got the whole universe in the local database? Anyhow, that narrows it down - I have to arrange for a branch for each release I want to "sticky". I must say I like the idea of the H: tag ... On 24/08/06, Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]> on Thu, 24 Aug 2006 17:40:17 +0100, "Andy Jones" <[EMAIL PROTECTED]> said: andyjwork> Alternatively I could just write a script that did 'mtn update -r t:test' ! andyjwork> andyjwork> (Um, that +would+ get the +latest+ revision with that tag, right?) No, if there is more than one revision tagged with 'test', I think you'd get an error asking you to disambiguate between all the revision ids. I've a branch, nvm.levitte.select-heads-of, that adds a magic selector H: that simply selects the headmost revision of the following selector, so you could say 'mtn update -r H:t:test'. It *is* a hack, though, more work is needed to make it worthy of mainline. You might be interested in http://www.venge.net/monotone/wiki/MagicSelectors btw. Cheers, Richard ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
