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

Re: [PATCH v2] t7800: fix racy "difftool --dir-diff syncs worktree" test

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 1, 2026, 22:49 UTC
Message-ID
<xmqqtsx5c5in.fsf@gitster.g>
In-Reply-To
<pull.2149.v2.git.git.1767292068036.gitgitgadget@gmail.com>
"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.
Previous: Paul Tarjan via GitGitGadgetNext: Phillip Wood
Message 4 of 11 in “t7800: fix racy "difftool --dir-diff syncs worktree" test”
  1. t7800: fix racy "difftool --dir-diff syncs worktree" testPaul Tarjan via GitGitGadget, Dec 31, 2025
  2. Johannes SchindelinJan 1, 2026
  3. t7800: fix racy "difftool --dir-diff syncs worktree" testPaul Tarjan via GitGitGadget, Jan 1, 2026
  4. Junio C HamanoJan 1, 2026
  5. Phillip WoodJan 3, 2026
  6. Paul TarjanJan 3, 2026
  7. Johannes SchindelinJan 3, 2026
  8. Junio C HamanoJan 4, 2026
  9. t7800: fix racy "difftool --dir-diff syncs worktree" testPaul Tarjan via GitGitGadget, Jan 3, 2026
  10. Junio C HamanoJan 4, 2026
  11. Phillip WoodJan 5, 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.