Re: [PATCH 2/2] refs: add GIT_REF_URI to specify reference backend and directory

From: Karthik Nayak <karthik.188@gmail.com>
Date: Nov 24, 2025, 13:25 UTC
Message-ID: <CAOLa=ZTn5UEqifJrJcVfCt=YyVOa3CMdLRsLpG=g4x2vmDPeKQ@mail.gmail.com>
In-Reply-To: <xmqq34675pz1.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 14 quoted lines

> Toon Claes <toon@iotcl.com> writes:
>
>>>     <ref_backend>://<path>
>>
>> I like this idea. This would allow us in the future to also do something
>> like:
>>
>>     reftable+nfs://10.11.12.13/ref-dir
>
> I actually thought from Karthik's definition that what you are
> trying to say is spelled more like this:
>
>     reftable://nfs://10.11.12.13/ref-dir
>

You're indeed correct.

Show 6 quoted lines

> IOW, the underlying URI to "reach the resource" is in the <path>
> part (i.e., "nfs://<addr>/<directory>").  And I found it somewhat a
> strange syntax, because the "to reach the resource, visit this" URI
> may not necessarily look like <path>, and I also wondered if
> spelling it like <ref_backend>:<URI-for-resource> is more
> appropriate.

This is a much better way to state what I was going for, I was considering the entire <ref_backend>:<path> as the URI since currently we only deal with FS paths (for files and reftable). But that could potentially change. As such, it makes sense to state it as <ref_backend>:<URI-for-resource>. Will modify accordingly.

Thanks.