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

Re: [PATCH v2] fsmonitor: check the untracked cache after a trivial response

From
Derrick Stolee <stolee@gmail.com>
Date
Nov 9, 2026, 20:47 UTC
Message-ID
<fefa2680-695c-41db-9975-7e972590b969@gmail.com>
In-Reply-To
<pull.2247.v2.git.1794251653636.gitgitgadget@gmail.com>
On 11/9/2026 2:14 PM, Ilia via GitGitGadget wrote:
>     Changes since v1:
>     
>      * the whole untracked cache is dropped if !worktree
>      * removed the comments as per nits
Thanks for these improvements. The v2 patch LGTM.
>      * rebased against ToT

Generally, you shouldn't do this as the maintainer will apply your patch in the same spot and handle most merge conflicts via rerere, but rebasing interrupts that. The main exception is when you rebase onto a specific topic or with regards to a large refactor that merged recently.

Thanks, -Stolee

Previous: Ilia via GitGitGadgetNext: Junio C Hamano
Message 6 of 8 in “fsmonitor: check the untracked cache after a trivial response”
  1. fsmonitor: check the untracked cache after a trivial responseIlia via GitGitGadget, Oct 4, 2026
  2. Derrick StoleeNov 5, 2026
  3. Junio C HamanoNov 5, 2026
  4. Ilia KNov 9, 2026
  5. fsmonitor: check the untracked cache after a trivial responseIlia via GitGitGadget, Nov 9, 2026
  6. Derrick StoleeNov 9, 2026
  7. Junio C HamanoNov 9, 2026
  8. Junio C HamanoNov 9, 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.