[merge] tags in repository

[Gustavo Niemeyer]

> Good for you. Not so good for someone who has put several projects to
> same repository. When that someone pushes or someone other pulls from
> him/her, all the other project tags go too. 

That situation should be considered when designing the conflict
resolution scheme.  If there's an ancestry graph for tags,
it should be possible to see that these tags don't have a
common ancestor, and thus provide a conflict resolution option,
or at least warn the user about the issue.

> Essentially this forces to keep separate projects in separate
> repositories. I don't like it. For me it has been useful to be
(...)

Not necessarily. If you're in control of the projects in that
repository, you may use a naming scheme that prevents conflicts.

-- 
Gustavo Niemeyer
http://niemeyer.net