Re: [PATCH v8 5/6] refs: allow reference location in refstorage config
On Tue, Feb 24, 2026, at 14:09, Karthik Nayak wrote:
Show 46 quoted lines
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
>
>> On Mon, Feb 23, 2026, at 09:01, Karthik Nayak wrote:
>>[snip]
>> It looks like dropping the list continuations fixes it.
>>
>> Supported format names are:
>>
>> include::../ref-storage-format.adoc[]
>>
>> The payload is passed directly to the reference backend. For the files and
>> [...]
>>
>> Maybe because you are inside an open block? I don’t know.
>>
>
> I don't know either. But this seems to fix it, let me know if it does
> for you too.
>
> --8<--
>
> diff --git a/Documentation/config/extensions.adoc
> b/Documentation/config/extensions.adoc
> index 3e51da36d3..329d02b3c4 100644
> --- a/Documentation/config/extensions.adoc
> +++ b/Documentation/config/extensions.adoc
> @@ -67,13 +67,13 @@ refStorage:::
> format and payload (e.g., `reftable:///foo/bar`).
>
> Supported format names are:
> -+
> +
> include::../ref-storage-format.adoc[]
> -+
> +
> The payload is passed directly to the reference backend. For the files and
> reftable backends, this must be a filesystem path where the references will
> be stored. Defaulting to the commondir when no payload is provided. Relative
> -paths are resolved relative to the $GIT_DIR. Future backends may support
> +paths are resolved relative to the `$GIT_DIR`. Future backends may support
> other payload schemes, e.g., postgres://127.0.0.1:5432?database=myrepo.
> --
> +
>
>
>>>[snip]