Re: What's cooking in git.git (Nov 2024, #10; Thu, 28)

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 2, 2024, 00:39 UTC
Message-ID: <xmqqy10ylxzp.fsf@gitster.g>
In-Reply-To: <fbda37b9-41e7-4b18-a831-dfb5a9a9c54f@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

Show 23 quoted lines

> Hi Junio
>
> On 28/11/2024 05:35, Junio C Hamano wrote:
>> * cw/worktree-extension (2024-11-26) 8 commits
>>   - worktree: refactor `repair_worktree_after_gitdir_move()`
>>   - worktree: add relative cli/config options to `repair` command
>>   - worktree: add relative cli/config options to `move` command
>>   - worktree: add relative cli/config options to `add` command
>>   - worktree: add `write_worktree_linking_files()` function
>>   - worktree: refactor infer_backlink return
>>   - worktree: add `relativeWorktrees` extension
>>   - setup: correctly reinitialize repository version
>>   Introduce a new repository extension to prevent older Git versions
>>   from mis-interpreting worktrees created with relative paths.
>>   Will merge to 'next'?
>>   source: <20241125-wt_relative_options-v5-0-356d122ff3db@pm.me>
>
> I've had a look at the range-diff for the latest version and had a
> query about the removal of a check from one of the tests[1]. Perhaps
> we should wait to hear from Caleb about that, but if you're keen to
> get these merged down in time for the next release we could just fix
> up the test later if it turns out to be necessary - I think the code
> changes are all fine.

Thanks for reviewing (and thanks Caleb for working on) this topic. I see the latest iteration v6 has added back the extension checking, so we probably are good to go.