From: Caleb White <cdwhite3@pm.me>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Phillip Wood <phillip.wood123@gmail.com>,
shejialuo <shejialuo@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PATCH v3 0/5] Optionally link worktrees with relative paths
Date: Fri, 25 Oct 2024 21:11:30 +0000 [thread overview]
Message-ID: <D5572ICCKQXT.3UQ8AJ2GSUZIP@pm.me> (raw)
In-Reply-To: <ZxwIEcUKMELmxeMh@nand.local>
On Fri Oct 25, 2024 at 4:05 PM CDT, Taylor Blau wrote:
> On Fri, Oct 25, 2024 at 08:57:17PM +0000, Caleb White wrote:
>> Caleb White (5):
>> worktree: refactor infer_backlink() to use strbuf*
>> worktree: support worktrees linked with relative paths
>> worktree: optionally link worktrees with relative paths
>> worktree: add test for path handling in linked worktrees
>> worktree: add `relativeWorktrees` extension
>
> The previous round was already merged to 'master' a few days ago[1],
> after merging it to 'next' and saying so in this[2] WC report.
>
> I'm not sure if you intended to send this series as a follow-up to the
> state that was already merged to 'master', or if you had intended to
> send a new round of changes not knowing it had already been merged.
>
> In either case, can you please send a new round based on the current tip
> of 'master'?
>
> Thanks,
> Taylor
>
> [1]: 8e08668322 (Merge branch 'cw/worktree-relative', 2024-10-22).
> [2]: https://lore.kernel.org/git/ZxLI06smvMuf%2FcT2@nand.local/
Ah, I must've missed that---I was in the process of working on v4 and
didn't realize that it had already been merged to master.
I'll send a new round based on the current tip of master.
Thanks!
Caleb
next prev parent reply other threads:[~2024-10-25 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 20:57 [PATCH v3 0/5] Optionally link worktrees with relative paths Caleb White
2024-10-25 20:57 ` [PATCH v3 1/5] worktree: refactor infer_backlink() to use strbuf* Caleb White
2024-10-25 20:57 ` [PATCH v3 2/5] worktree: support worktrees linked with relative paths Caleb White
2024-10-25 20:57 ` [PATCH v3 3/5] worktree: optionally link worktrees " Caleb White
2024-10-25 20:57 ` [PATCH v3 4/5] worktree: add test for path handling in linked worktrees Caleb White
2024-10-25 20:57 ` [PATCH v3 5/5] worktree: add `relativeWorktrees` extension Caleb White
2024-10-25 20:59 ` [PATCH v3 0/5] Optionally link worktrees with relative paths Caleb White
2024-10-25 21:05 ` Taylor Blau
2024-10-25 21:11 ` Caleb White [this message]
2024-10-25 21:38 ` Taylor Blau
2024-10-25 22:34 ` Caleb White
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=D5572ICCKQXT.3UQ8AJ2GSUZIP@pm.me \
--to=cdwhite3@pm.me \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=me@ttaylorr.com \
--cc=phillip.wood123@gmail.com \
--cc=shejialuo@gmail.com \
--cc=sunshine@sunshineco.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 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.