Exactly: multiple tags can't be prevented. And monotone does cope with them. It's just that they don't work in quite the way you might expect.
::grin:: you mean that it copes with them by raising an error? Must be some strange new definition of "cope" that I was previously unaware of... Thinking about this some more, I do see your dilemma. If the t: selector implemented the last tag of that name then you would let yourself in for some unpleasant behaviour, because someone else could have used the same tag. t:tag could mean different things before and after a sync. Of course, you could specify both the tag name and the author, and presumably that would be safe ... but for monotone to deal with that would be too much magic for me. It rather looks as if tags are only useful to avoid you having to remember hashes; and to mark the points where the code leaves the VCS. _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel