On Sun, Feb 06, 2011 at 09:09:26AM -0500, Nicolas Pitre wrote: > On Sun, 6 Feb 2011, Dmitry Potapov wrote: >_ > > To me, the proper handling ambiguity means that when I do "git fetch" I > > immediately see warning about tag clashes. >_ > Fair enough. >_ > > So, I agree with you that > > current behavior is not good, but I disagree with you about having many > > namespaces, because it postpones detection of the conflict until I try > > to use. >_ > No. The later does not prevent the former. But what if I really have two semi-related projects that I want to fetch into the same repository as Johan suggested? In this case, I want to have separate namespaces and no warning when I fetch. >_ > Of course there is a reason. What if your fetch brings in hundreds of_ > tags (this is common for some projects) and then you want to remove that_ > fetched branch from your repository? How do you determine which tag_ > came from that remote repository and which tags are to be kept? Without_ > a separate namespace this is practically impossible. Well, I see your use case now. Maybe the right solution is add an option that will tell whether to fetch tags into separate namespace or not, and later based on experiences, we can decide whether we want to change the default to have separate namespaces for tags. 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