git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Aug 15, 2026, 14:33 UTC
Message-ID
<aoB4pOTtJ65PjwPA@fruit.crustytoothpaste.net>
In-Reply-To
<CAOqWQb+XY_u2OUNnBJ9GBGBz8B73ocHWp+V1tDBS-4a5-OviYA@mail.gmail.com>
On 2026-08-14 at 13:29:26, Peter Morris wrote:
Show 7 quoted lines
> The PR says it only supports Linux and macOS, but ReFS
> is available on Windows too.
> 
> I believe that if the source and destination are on the same ReFS
> volume the Windows CopyFile API will use block cloning automatically,
> so if CopyFile were used we would get this for free on Windows Dev
> Drives.

ReFS has serious defects in its implementation. If the data has been written but not flushed to disk, the resulting copy will be corrupt. I just saw this come in with Git LFS[0] and I described it to a colleague as "horribly broken". I definitely don't recommend adding support for this to Git until only fixed versions of Windows are publicly available.

[0] https://github.com/git-lfs/git-lfs/issues/6312
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Peter MorrisNext: Peter Morris
Message 7 of 8 in “[RFC] git worktree: use filesystem cloning where supported”
  1. Peter MorrisAug 14, 2026
  2. Kristoffer HaugsbakkAug 14, 2026
  3. Junio C HamanoAug 14, 2026
  4. Peter MorrisAug 15, 2026
  5. Kristoffer HaugsbakkAug 14, 2026
  6. Peter MorrisAug 14, 2026
  7. brian m. carlsonAug 15, 2026
  8. Peter MorrisAug 15, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.