From: Junio C Hamano <gitster@pobox•com>
To: "Paul Tarjan via GitGitGadget" <gitgitgadget@gmail•com>
Cc: git@vger•kernel.org, Paul Tarjan <github@paulisageek•com>
Subject: Re: [PATCH v2] t7800: fix racy "difftool --dir-diff syncs worktree" test
Date: Fri, 02 Jan 2026 07:49:52 +0900 [thread overview]
Message-ID: <xmqqtsx5c5in.fsf@gitster.g> (raw)
In-Reply-To: <pull.2149.v2.git.git.1767292068036.gitgitgadget@gmail.com> (Paul Tarjan via GitGitGadget's message of "Thu, 01 Jan 2026 18:27:48 +0000")
"Paul Tarjan via GitGitGadget" <gitgitgadget@gmail•com> writes:
> Range-diff vs v1:
>
> 1: dd5b774451 = 1: 98bc88f336 t7800: fix racy "difftool --dir-diff syncs worktree" test
In other words, absolutely no change?
But that is fine. It is clear that these changes would work around
the problem with racily clean index entries.
Are there things we could do to help "difftool"?
For example, would it help to add a new option to "git update-index"
so that scripts can say "I updated this file in the working tree,
mark it as potentially racily dirty", and use it in "difftool",
perhaps, or something?
Queued. Thanks.
next prev parent reply other threads:[~2026-01-01 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 22:19 [PATCH] t7800: fix racy "difftool --dir-diff syncs worktree" test Paul Tarjan via GitGitGadget
2026-01-01 14:49 ` Johannes Schindelin
2026-01-01 18:27 ` [PATCH v2] " Paul Tarjan via GitGitGadget
2026-01-01 22:49 ` Junio C Hamano [this message]
2026-01-03 9:39 ` Phillip Wood
2026-01-03 16:30 ` Paul Tarjan
2026-01-03 20:29 ` Johannes Schindelin
2026-01-04 2:27 ` Junio C Hamano
2026-01-03 20:40 ` [PATCH v3] " Paul Tarjan via GitGitGadget
2026-01-04 2:34 ` Junio C Hamano
2026-01-05 10:33 ` Phillip Wood
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=xmqqtsx5c5in.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitgitgadget@gmail$(echo .)com \
--cc=github@paulisageek$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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