From: Caleb White <cdwhite3@pm.me>
Date: Tue, 22 Oct 2024 04:32:17 GMT
Subject: Re: [PATCH v3 2/3] worktree: link worktrees with relative paths
Message-ID: <D521XSJ9N80C.19U6V5T7LCRSB@pm.me>
In-Reply-To: <xmqqfrp4onjd.fsf@gitster.g>

On Wed Oct 9, 2024 at 6:37 PM CDT, Junio C Hamano wrote:
> If we are talking about making irreversible change to an existing
> repository, we may need to grab one extensions bit (cf.
> Documentation/technical/repository-version.txt and then refer also
> to Documentation/config/extensions.txt [*]) and flip it when we
> wrote a relative link to refer to an worktree and repository.

This has been implemented.

> [Footnote]
>
>  * The repository-version document claims that any extensions
>    invented must be registered there, but config/extensions.txt that
>    came later ignored it and seems to have acquired a few more than
>    the "master list".  We should clean up the mess.

I cleaned up the mess in a separate patch[1].


[1]: https://lore.kernel.org/git/20241021-cleanup-extension-docs-v1-1-ab02cece3132@pm.me

Best,