[merge] tags in repository

[Lukáš Lalinský]

On Pi, 2007-01-26 at 22:00 +0200, Alexander Belchenko wrote:
> > I would like versioned tags that are part of a branch and not repository.
> 
> This is really *bad* thing, IMO. Because in this case you easily go to in situation
> when you will have several branches of one project with only tag in one branch.

I think it's better to have no tag, rather than a tag that points to a
revision that is missing in the branch. With per-branch tags, it would
be guaranteed that all tags accessible from a branch are valid. With
per-repository tags you can't guarantee this, because updating one
branch adds tags to all other branches in the repository.

> Or with one tag that points to different revisions in different branches.
> And in latter case you get different result when using tag with the same name
> in different branches. Because this is implicit it will guide to big problems
> when you'll need to dig to deep to understand why different branches
> of the same projects behaves differently.

Actually, this problem is even more visible in per-repository tags
because they are supposed to be globally unique. Personally, I don't
believe people will respect this, they will use tags like "1.5.0"
instead of "myproject-1.5.0", which will lead to even more conflicts.

-Lukáš