On 12-04-26 02:40 PM, Nathan Gray wrote: > Hey guys, > > Namespacing works really well for branch refs. I know that > remotes/origin/master is origin's master branch. I may or may not > have a master branch, and it may or may not have anything in common > with origin's. Our repositories are independent, after all, so it > makes sense that our refs would live in different namespaces. > > So why is it that tag refs don't follow this model? Why is my > "best-commit-ever" tag assumed to be the same as origin's? Given a > ref in refs/tags it's unclear if the ref is public, private, on origin > or not on origin. Will pushing my tags create anything new or not? > Who knows? Compare this to branches, where the same questions are > easy to answer thanks to namespacing. There was lengthy, but inconclusive, discussion about this a year ago: http://thread.gmane.org/gmane.comp.version-control.git/165799/focus=166290 M. -- 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