Re: [RFC] git worktree: use filesystem cloning where supported

Peter Morris <[email protected]>
Newsgroups org.kernel.vger.git
Message-ID <CAOqWQbKuD_u5d8XbZ=6x9qc61EXNj9hDQjRfe=XE1FkWCp45bg@mail.gmail.com>
> On Fri, 14 Aug 2026 at 17:29, Junio C Hamano <[email protected]> wrote:
> In that thread, Brian makes a good point that you cannot "copy"
> dirty working tree files from an existing worktree, and also that
> you cannot have the same branch checked out in multiple worktrees at
> the same time, to avoid making other worktrees out of sync when a
> commit is made in one of the worktrees to advance the branch tip.
> [snip]

Hi Junio,

Thanks for the detailed reply. That makes sense, and it's useful to
know that the approach is technically viable.

I'm afraid I'm not sufficiently familiar with Git's internals to take
this on myself, but hopefully someone with more experience in that
area might be interested in implementing it.

I've seen lots of complaints about Solid State Drives dying due to
worktree use. I personally have a repo containing over 80GB of images
that never change, so currently worktrees just aren't an option for
me. I hope this will change in the near future!

Pete
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.