Re: What's cooking in git.git (Mar 2022, #06; Mon, 28)

> 
> * jh/builtin-fsmonitor-part2 (2022-03-25) 30 commits
>   - t7527: test status with untracked-cache and fsmonitor--daemon
>   - fsmonitor: force update index after large responses
>   - fsmonitor--daemon: use a cookie file to sync with file system
>   - fsmonitor--daemon: periodically truncate list of modified files
>   - t/perf/p7519: add fsmonitor--daemon test cases
>   - t/perf/p7519: speed up test on Windows
>   - t/perf/p7519: fix coding style
>   - t/helper/test-chmtime: skip directories on Windows
>   - t/perf: avoid copying builtin fsmonitor files into test repo
>   - t7527: create test for fsmonitor--daemon
>   - t/helper/fsmonitor-client: create IPC client to talk to FSMonitor Daemon
>   - help: include fsmonitor--daemon feature flag in version info
>   - fsmonitor--daemon: implement handle_client callback
>   - compat/fsmonitor/fsm-listen-darwin: implement FSEvent listener on MacOS
>   - compat/fsmonitor/fsm-listen-darwin: add MacOS header files for FSEvent
>   - compat/fsmonitor/fsm-listen-win32: implement FSMonitor backend on Windows
>   - fsmonitor--daemon: create token-based changed path cache
>   - fsmonitor--daemon: define token-ids
>   - fsmonitor--daemon: add pathname classification
>   - fsmonitor--daemon: implement 'start' command
>   - fsmonitor--daemon: implement 'run' command
>   - compat/fsmonitor/fsm-listen-darwin: stub in backend for Darwin
>   - compat/fsmonitor/fsm-listen-win32: stub in backend for Windows
>   - fsmonitor--daemon: implement 'stop' and 'status' commands
>   - fsmonitor--daemon: add a built-in fsmonitor daemon
>   - fsmonitor: document builtin fsmonitor
>   - fsmonitor: use IPC to query the builtin FSMonitor daemon
>   - fsmonitor: config settings are repository-specific
>   - fsmonitor-ipc: create client routines for git-fsmonitor--daemon
>   - fsmonitor: enhance existing comments, clarify trivial response handling
>   (this branch is used by jh/builtin-fsmonitor-part3.)
> 
>   Built-in fsmonitor (part 2).
> 
>   Will merge to 'next'?
>   source: <pull.1041.v9.git.1648231393.gitgitgadget@gmail.com>
>