Re: [PATCH 06/12] fsmonitor: clarify handling of directory events in callback

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 20, 2024, 19:24 UTC
Message-ID: <xmqqjzmzndli.fsf@gitster.g>
In-Reply-To: <b379b92f-407a-c4b3-ee65-a7fa6e7dff74@jeffhostetler.com>

Jeff Hostetler <git@jeffhostetler.com> writes:

> I'll split this into 2 commits.  One for the refactor and one for
> the new return value.

And the latter one that makes the return value richer contains the caller that makes use of the returned value? That's great. It would make it very much easier to read the resulting commit, as the presence of the callers and how they use the returned value would make it self evident why it makes sense to return the number of entries invalidated.

Thanks.

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