Marc Branchaud <marcnarc@xxxxxxxxxxx> writes: > Tags don't become "official" until they're published according to the > project's process. For us git users, that means the tag appears in > git.kernel.org/pub/scm/git/git.git. A tag that appears somewhere else can > have all sorts of meanings, but I don't think "official" could be one of them. I think you are essentially saying the same thing. Think of hiding the unofficial tags to refs/private-tags by "interim maintainer" (or public at large for that matter); they won't be published automatically, unless the publisher decides to publish "according to the project's process." As I said in my message, it feels awkward to use refs/private-tags for tags everybody uses for his or her own purpose, so by swapping the roles of namespaces around, we would be able to use refs/tags for private ones, and refs/remotes/origin/tags for the ones that came from upstream. But then if you fetch/pull from a third party (including the "interim maintainer"), it feels wasteful to get full set of tags that you have in the origin namespace anyway replicated in refs/remotes/interim/tags. And that is what bothers me---not the waste itself, but I have this nagging feeling that the wasteful duplication is an indication of something else designed wrong. -- 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