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

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 21, 2025, 16:07 UTC
Message-ID: <xmqq34675pz1.fsf@gitster.g>
In-Reply-To: <87pl9b5wos.fsf@iotcl.com>

Toon Claes <toon@iotcl.com> writes:

Show 6 quoted lines

>>     <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

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.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.