Re: [PATCH v7 04/12] fsmonitor: teach git to optionally utilize a file system monitor to speed up detecting new or changed files.

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 22, 2017, 01:02 UTC
Message-ID: <xmqqlgl7mtoe.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <f50825a4-fa15-9f28-a079-853e78ee8e2e@gmail.com>

Ben Peart <peartben@gmail.com> writes:

> Since the fsmonitor data can be trusted and is kept in sync with the
> working directory, the only remaining valid uses are those locations
> where we don't want to trigger an unneeded refresh_fsmonitor() call.

Now that is a lot more assuring ;-) And the exceptions below also make sense to me.

Thanks for thinking this through.

$ 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.