From: Junio C Hamano <gitster@pobox.com>
To: Caleb White <cdwhite3@pm.me>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #10; Thu, 28)
Date: Mon, 02 Dec 2024 11:48:10 +0900 [thread overview]
Message-ID: <xmqq8qsykdg5.fsf@gitster.g> (raw)
In-Reply-To: <D5Y4Z7I3PJW2.C2AE3WAKRLLH@pm.me> (Caleb White's message of "Thu, 28 Nov 2024 21:40:28 +0000")
Caleb White <cdwhite3@pm.me> writes:
> 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.
Yup, v6 looks good. Will queue. Thanks.
next prev parent reply other threads:[~2024-12-02 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 21:40 What's cooking in git.git (Nov 2024, #10; Thu, 28) Caleb White
2024-12-02 2:48 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-28 5:35 Junio C Hamano
2024-11-28 15:34 ` Phillip Wood
2024-12-02 0:39 ` Junio C Hamano
2024-11-28 16:11 ` Patrick Steinhardt
2024-12-02 0:48 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8qsykdg5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=cdwhite3@pm.me \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.