Re: [PATCH 0/4] Link worktrees with relative paths
- From
Caleb White <cdwhite3@pm.me>
- Date
- Oct 6, 2024, 05:11 UTC
- Message-ID
- <zKUnWY8u1SJNeS4oLK85znjacgYJJeN8HefenwaJ9B9Q1YrQAumpAxWos4svaawkTfQZ_HaS3yp6WrOQQI7yt3ZO0UMCfkM0lJDDnMD-Lno=@pm.me>
- In-Reply-To
- <CAPig+cTB-sA-g4cdhfEjWwY1mnbWJ41e=bOCNwp=Y8JKvpmpRg@mail.gmail.com>
On Sunday, October 6th, 2024 at 00:04, Eric Sunshine <sunshine@sunshineco.com> wrote:
> On Sun, Oct 6, 2024 at 12:59 AM Caleb White cdwhite3@pm.me wrote: >
Show 12 quoted lines
> > This patch series modifies Git's handling of worktree linking to use > > relative paths instead of absolute paths. The motivation behind this > > change is to enhance the robustness of worktree links when the main > > repository is moved, or when used in environments like containerized > > development where absolute paths differ across systems. > > [...] > > Caleb White (4): > > worktree: refactor infer_backlink() to use *strbuf > > worktree: link worktrees with relative paths > > worktree: sync worktree paths after gitdir move > > worktree: prevent null pointer dereference >
>
> Unfortunately, these patches are whitespace-damaged. Can you please > resubmit using either `git send-email` or GitGitGadget[1]? >
> [1]: https://gitgitgadget.github.io/
I sent them with `git send-email`, let me try again and then if that doesn't work then I'll try GitGitGadget. Just out of curiosity, how could you tell that they are whitespaced-damaged (so I know what to look for)?
Thanks,