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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sunday, October 6th, 2024 at 00:04, Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote:

> On Sun, Oct 6, 2024 at 12:59 AM Caleb White cdwhite3@xxxxx wrote:
> 

> > 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,

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux