On Mon, Feb 07, 2011 at 12:22:51AM +0100, Johan Herland wrote: > > As Nicolas mentioned elsewhere in the thread, having separate tag namespaces > does not prevent us from also warning about ambiguous tag names on fetch. > With separate namespaces, you could probably implement such a warning more > easily as a hook, instead of hacking the fetch code directly. Since when we started to handle the common case by forcing each user to write some hook (BTW, which one?), while having an uncommon case as the default? It makes no sense. And Nicolas suggested something different -- always warn on fetch, which means there will be warnings in your case where you have two projects in one repo. Dmitry -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html