Re: enhanced remote ref namespaces

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 12, 2015, 19:49 UTC
Message-ID: <xmqqwpx0jnhc.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CA+P7+xq_v+TjqSDC3aR2bdUmCJyj=zLXSE5SbVgOEr+SojOUQQ@mail.gmail.com>

Jacob Keller <jacob.keller@gmail.com> writes:

> That still hasn't really resolved the question of how to deal with
> tags, but it does solve the question of how to deal with replace and
> notes refs.

I do not think it would be a good change to add a

    [remote "foo"]
        fetch = refs/tags/*:refs/tracking/foo/tags/*

as people do expect to see tags from upstream to appear in their local tag namespace when cloning from the central meeting point of their project (e.g. Linus's kernel repository).

I'm willing to believe those who argued that they have both private tags and public tags in their repository, but I think that would be something better supported by adding "git tag --local foo" that creates a local tag in e.g. refs/local-tags/foo, and by teaching DWIMmery to also look in there when the user says "foo".

Alternatively, they can use their local branch namespace, which is already private to them.