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

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

 



On Sun, Oct 6, 2024 at 1:04 AM 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.
>
> Unfortunately, these patches are whitespace-damaged. Can you please
> resubmit using either `git send-email` or GitGitGadget[1]?

Also, since you're touching infer_backlink(), see [1] which makes some
changes nearby.

And you might be interested in [2] which may indicate that there are
some holes in the tests around worktrees which might need filling.
(Since your patches are whitespace-damaged, I haven't checked whether
your series succeeds or fails in the way the series to which [2] is a
response fails.)

[1]: https://lore.kernel.org/git/20240923075416.54289-1-ericsunshine@xxxxxxxxxxx/
[2]: https://lore.kernel.org/git/CAPig+cQXFy=xPVpoSq6Wq0pxMRCjS=WbkgdO+3LySPX=q0nPCw@xxxxxxxxxxxxxx/





[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