Re: proposal for how to share other refs as part of refs/tracking/*

From: Jacob Keller <jacob.keller@gmail.com>
Date: Jun 14, 2017, 01:24 UTC
Message-ID: <CA+P7+xqeAxtNqKLXtYs6pW9eEZLK-jVwjfX25mtZVe51W+yH6Q@mail.gmail.com>
In-Reply-To: <010f8a1b-cab3-fada-0f38-1f0726283f5e@xiplink.com>

On Tue, Jun 13, 2017 at 8:55 AM, Marc Branchaud <marcnarc@xiplink.com> wrote:

Show 19 quoted lines

> On 2017-06-13 10:41 AM, Marc Branchaud wrote:
>>
>>
>> So I like your refs/tracking proposal, and hope that it aims for mirroring
>> a remote's refs, to eventually replace refs/remotes entirely.
>
>
> To be extra-clear:
>
> I think a refs/tracking hierarchy that starts with notes and maybe some
> other bits is a good first step.
>
> I *hope* such a first step can eventually mirror all of a remote's refs,
> including heads and tags.
>
> I in no way think that this effort should begin by tackling heads and tags.
>
>                 M.
>

As far as I understand it, mirroring all refs should be as simple as adding something like

refs/*:refs/tracking/<name>/*

assuming that * begins working for multiple components..

Now actually making *use* of that feature would be different.

However, this was generally the direction I was thinking of heading.

Thanks, Jake