Re: [PATCH 0/4] Link worktrees with relative paths

From: Caleb White <cdwhite3@pm.me>
Date: Oct 6, 2024, 06:05 UTC
Message-ID: <gX8RNUg1e1FCYFS1vP-uT4rbMpg21Ax07CZm5Ha7Dsk93EN6CTuXiLr3boTaoNEi71O1rDoUxhTs6KQt7Cvfz7B3KlbpZzis5b05KW7ARls=@pm.me>
In-Reply-To: <CAPig+cQE0RNLhktuja-BbF8WwZmKC3cox_GUC-o4w87PadDpgw@mail.gmail.com>

On Sunday, October 6th, 2024 at 00:50, Eric Sunshine <sunshine@sunshineco.com> wrote:

> On Sun, Oct 6, 2024 at 1:41 AM Caleb White cdwhite3@pm.me wrote:
>

> > On Sunday, October 6th, 2024 at 00:32, Eric Sunshine sunshine@sunshineco.com wrote:
> >

> > > It's broken in the Git mailing list archive, as well. If you search
> > > for "mbox.gz" at [], you can download this email thread. The patches
> > > in that mbox file have the same damage as I'm seeing.
> >

> > That's interesting...what's the best way to try and resubmit? As
> > a new thread or as a v2?
>

> For continuity in the archive, probably best to submit it as v2 as a
> reply to the original cover letter:
>

> git send-email -v2 --reply-to='20241006045847.159937-1-cdwhite3@pm.me' ...

Thanks, I regenerated v2 patches with `format-patch` and then sent with `send-email`. However, the issue seems to have persisted (at least it's consistent?). I looked through the the patches on the listserv and that seems to be the only location where this occurs.