From: Caleb White <cdwhite3@pm.me>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: What's cooking in git.git (Nov 2024, #08; Fri, 22)
Date: Fri, 22 Nov 2024 14:31:45 +0000 [thread overview]
Message-ID: <D5SS3P7WQG4F.1I20Z59IDQMD1@pm.me> (raw)
On Fri Nov 22, 2024 at 4:11 AM CST, Junio C Hamano wrote:
> * cw/worktree-extension (2024-11-01) 9 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
> - Merge branch 'cw/config-extensions' into cw/worktree
>
> Introduce a new repository extension to prevent older Git versions
> from mis-interpreting worktrees created with relative paths.
>
> Needs review.
> source: <20241031-wt_relative_options-v4-0-07a3dc0f02a3@pm.me>
This latest round has been reviewed by Philip (cc'd) and I've addressed
his comments (mainly in regards to using test functions I was unaware
of). I was waiting for more comments before rerolling but if I don't
hear anything in the next few days I'll go ahead and do that.
Please let me know if there's anything else I can do to help move this
along, it would be good to get this in before 2.48 is released.
Best,
Caleb
next reply other threads:[~2024-11-22 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 14:31 Caleb White [this message]
2024-11-25 0:25 ` What's cooking in git.git (Nov 2024, #08; Fri, 22) Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 10:11 Junio C Hamano
2024-11-22 19:10 ` Philippe Blain
2024-11-25 0:23 ` 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=D5SS3P7WQG4F.1I20Z59IDQMD1@pm.me \
--to=cdwhite3@pm.me \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).