Git development
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jason Newton <nevion@gmail.com>
Cc: Jason Newton via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v2 1/2] worktree: add --reflink for copy-on-write worktree creation
Date: Thu, 22 Oct 2026 22:31:06 +0000	[thread overview]
Message-ID: <atqOqRE866bgyxfL@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <CAGou9MhkmSZs3ViSj6qqkZY6LLLQQ+5RzjLG5EhM-AXx+d7h=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]

On 2026-10-21 at 07:15:50, Jason Newton wrote:
> Brian,

Hay,

> macOS cp has no --reflink=always. The clone option is -c, which is
> clonefile(2). t/t2400-worktree-add.sh already probes that way. The
> REFLINK prerequisite runs "cp -c" when the MACOS prerequisite is set,
> and "cp --reflink=always" otherwise. The test that depends on REFLINK
> is "--reflink carries untracked files and reconciles changes".
> 
> That is in 042485f0e9cd8cf1765b811ea7334247aec44971. The pull request
> CI for that commit is the APFS run:
> 
> https://github.com/git/git/pull/2317
> https://github.com/git/git/actions/runs/39502233266
> 
> All four macos-14 jobs succeeded. The runners were macOS 14.8.9
> (23J631), image macos-14-arm64 20260831.0302.1. "print test failures"
> was skipped on each job, which is the step that runs only when a test
> script fails.

You have a test_lazy_prereq for REFLINK in your test file and it uses
`cp --reflink=always`.  If that doesn't work on macOS, then the
prerequisite fails, so the test with the REFLINK prerequisite is
skipped.  That means it doesn't fail, but it also doesn't run, so it
isn't testing anything at all.

What I'm saying is that it should actually pass the REFLINK prerequisite
and run the test on macOS.  It looks like you did do that in v3, which
is good.

It also looks like at the very least substantial portions of this email
are the output of an LLM.  You should read and understand our AI
policy[0].  In any event, I'm not going to review or respond further to
AI slop, especially since I work on Git entirely in my personal time and
my time is currently quite limited.

We consider it important to explain our patches and our thought process
well on this list and we have high standards for inclusion—as we
should—since many developers around the world depend on us.  You're
welcome to participate, but you should respond to other humans with your
own words and thoughts, since we're giving you the same time and
courtesy.  If I wanted to know what an LLM thinks about what I have to
say, I know where to find one—I wouldn't have asked.[1]

[0] https://git-scm.com/docs/SubmittingPatches#ai
[1] For the avoidance of doubt, these em dashes are my own creation and
come from my love of language and the fact that I have an English
degree.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]

  reply	other threads:[~2026-10-22 22:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 18:49 [PATCH 0/2] worktree: copy-on-write creation and shared-branch worktrees Jason Newton via GitGitGadget
2026-06-05 18:49 ` [PATCH 1/2] worktree: add --reflink for copy-on-write worktree creation Jason Newton via GitGitGadget
2026-06-05 18:49 ` [PATCH 2/2] worktree: allow sharing a checked-out branch across worktrees Jason Newton via GitGitGadget
2026-06-05 19:59 ` [PATCH 0/2] worktree: copy-on-write creation and shared-branch worktrees brian m. carlson
2026-06-08 14:36 ` Junio C Hamano
2026-10-20 16:04 ` [PATCH v2 0/2] worktree: copy-on-write creation and ephemeral branches Jason Newton via GitGitGadget
2026-10-20 16:04   ` [PATCH v2 1/2] worktree: add --reflink for copy-on-write worktree creation Jason Newton via GitGitGadget
2026-10-20 21:20     ` brian m. carlson
2026-10-21  7:15       ` Jason Newton
2026-10-22 22:31         ` brian m. carlson [this message]
2026-10-20 16:04   ` [PATCH v2 2/2] worktree: reap ephemeral branches created by "worktree add" Jason Newton via GitGitGadget
2026-10-21  6:52     ` Eric Sunshine
2026-10-21  7:40       ` Jason Newton
2026-10-21  8:06         ` Eric Sunshine
2026-10-21  8:28           ` Jason Newton
2026-10-21 14:03             ` Phillip Wood
2026-10-21 22:44               ` Jason Newton
2026-10-21  7:08   ` [PATCH v2 0/2] worktree: copy-on-write creation and ephemeral branches Eric Sunshine
2026-10-21  7:17 ` [PATCH v3 0/4] " Jason Newton via GitGitGadget
2026-10-21  7:17   ` [PATCH v3 1/4] worktree: add --reflink for copy-on-write worktree creation Jason Newton via GitGitGadget
2026-10-21  7:17   ` [PATCH v3 2/4] worktree: reap ephemeral branches created by "worktree add" Jason Newton via GitGitGadget
2026-10-21  7:17   ` [PATCH v3 3/4] worktree: disable reflink on Windows Jason Newton via GitGitGadget
2026-10-21  7:17   ` [PATCH v3 4/4] worktree: keep the reflink probe referenced " Jason Newton via GitGitGadget

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=atqOqRE866bgyxfL@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=nevion@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox