From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Johannes.Schindelin@gmx.de,
ki.stfu@gmail.com
Subject: Re: [PATCH] fsmonitor: invalidate untracked cache after losing history
Date: Thu, 05 Nov 2026 09:39:28 -0800 [thread overview]
Message-ID: <xmqqmrrnw52n.fsf@gitster.g> (raw)
In-Reply-To: <3d62a579-5bf1-4431-8bfc-757c3c873d80@gmail.com> (Derrick Stolee's message of "Thu, 5 Nov 2026 09:08:30 -0500")
Derrick Stolee <stolee@gmail.com> writes:
> Let me first see if we can take that patch instead of mine. I'll start
> some review over there.
Very much appreciated.
prev parent reply other threads:[~2026-11-05 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:37 [PATCH] fsmonitor: invalidate untracked cache after losing history Derrick Stolee via GitGitGadget
2026-11-04 20:39 ` Junio C Hamano
2026-11-04 22:52 ` Junio C Hamano
2026-11-05 14:08 ` Derrick Stolee
2026-11-05 15:02 ` Derrick Stolee
2026-11-05 17:39 ` Junio C Hamano [this message]
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=xmqqmrrnw52n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=ki.stfu@gmail.com \
--cc=stolee@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