On Friday 18 May 2007, Petr Baudis wrote: > The problem is ugly too, though - suddenly, you have created a SINGLE > UNIVERSE-WIDE NAMESPACE INSIDE A DISTRIBUTED VCS. And that's not going > to work well. Actually, tags are already such a namespace. If you want to merge two projects which have the same tag names, of course you still preserve the different tag objects, but only one will appear in the refs/tags namespace. So what is the best identifier for a subprobject? It is one that probably never clashes with any subproject identifier of another superproject. At least, it should not clash between any superprojects which ever could be a candidate for merging the two into one. Junios proposal using an URL as identifier actually is quite good in this regard, similar to JAVA package names. However, I wonder whether the possible merge of two superprojects into one is a real issue. When they use the same subprojects identifiers, there is a workaround: instead of merging, make one superproject the subproject of the other. Josef - 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
