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

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

> On Wed Nov 27, 2024 at 11:35 PM CST, 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>
>
> There is one test that I've updated (added a check that was accidentally
> removed). I can send that as a reroll if you'd like, otherwise I think
> this is ready to go.