Re: [1.8.0] Provide proper remote ref namespaces

From: Marc Branchaud <marcnarc@xiplink.com>
Date: Feb 7, 2011, 16:10 UTC
Message-ID: <4D501983.5060508@xiplink.com>
In-Reply-To: <7vvd0xvsjc.fsf@alter.siamese.dyndns.org>

On 11-02-06 03:04 PM, Junio C Hamano wrote:

Show 24 quoted lines

> Nicolas Pitre <nico@fluxnic.net> writes:
> 
>>> The latter seems like a regression for the common case of fetching from
>>> two upstreams. E.g., I usually pull from Junio, getting
>>> remotes/origin/v1.7.0.  One day Shawn is the interim maintainer, and I
>>> pull from him, getting remotes/spearce/v1.7.0, which he previously
>>> fetched from Junio. Under the current code, I can still do "git show
>>> v1.7.0"; under the scheme described above I now have to say
>>> "origin/v1.7.0" to disambiguate.
>>
>> Let's suppose that both tags are identical, as in your scenario above 
>> they would be, then there is no need to call for any ambiguity in that 
>> case.
> 
> I agree that we do not want refs/remotes/tags/*/that-tag-people-agree-on
> in that case.  We want to store a single copy and find it there, and that
> single copy has traditionally been found in refs/tags hierarchy.
> 
> I think the real issue is not necessarily that the location is shared with
> local tag namespace, but is the lack of a convenient way (or just BCP) to
> segregate what are local and what are official when transferring tags out
> of your repository.  That is what discourages people from using tags for
> their personal and ephemeral use, marking some points in their own work
> with personal tags that are never intended to be published.

That may be an issue, but I don't think it's the issue in this thread. Recall what Nicolas said:

	The extraordinary misfeature of the tag namespace at the
	moment comes from the fact that whenever you add a remote
	repo to fetch, and do fetch it, then your flat tag
	namespace gets polluted with all the tags the remote might
	have.  If you decide to delete some of those remote branches,
	the tags that came with it are still there and indistinguishable
	from other tags making it a real pain to sort out.

Those tags can all be properly "official" and still the problem exists.

In the "interim maintainer" case, I suggest it's not really a question of private-vs-official tags. Folks who clone directly from the maintainer should understand that some tags are works-in-progress. As the maintainer role gets passed from person to person (and repo to repo), it seems more useful to be able to distinguish work-in-progress tag vX.Y.Z as coming from maintainer A or B, i.e. tags A/vX.Y.Z and B/vX.Y.Z. If the tags point to the same commit then just "vX.Y.Z" resolves fine. But if the two maintainers have different ideas of what vX.Y.Z should be, then the fully-qualified names help to identify the differences.

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.

M.