On 9/13/21 10:02 PM, Junio C Hamano wrote: ...
* jh/builtin-fsmonitor (2021-09-03) 37 commits - fixup! fsmonitor--daemon: implement handle_client callback - SQUASH??? https://github.com/git/git/runs/3438543601?check_suite_focus=true#step:5:136 - BANDAID: sparse fixes - t7527: test FS event reporing on MacOS WRT case and Unicode - fsmonitor: handle shortname for .git - t7527: test status with untracked-cache and fsmonitor--daemon - fsmonitor: force update index after large responses - fsmonitor: enhance existing comments - fsmonitor--daemon: use a cookie file to sync with file system - fsmonitor--daemon: periodically truncate list of modified files - t7527: create test for fsmonitor--daemon - t/perf/p7519: add fsmonitor--daemon test cases - t/perf: avoid copying builtin fsmonitor files into test repo - t/perf/p7519: speed up test using "test-tool touch" - t/helper/test-touch: add helper to touch a series of files - fsmonitor--daemon: implement handle_client callback - fsmonitor-fs-listen-macos: implement FSEvent listener on MacOS - fsmonitor-fs-listen-macos: add macos header files for FSEvent - fsmonitor-fs-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: do not try to operate on bare repos - fsmonitor--daemon: implement 'start' command - fsmonitor--daemon: implement 'run' command - fsmonitor-fs-listen-macos: stub in backend for MacOS - fsmonitor-fs-listen-win32: stub in backend for Windows - t/helper/fsmonitor-client: create IPC client to talk to FSMonitor Daemon - fsmonitor--daemon: implement 'stop' and 'status' commands - fsmonitor--daemon: add a built-in fsmonitor daemon - fsmonitor: use IPC to query the builtin FSMonitor daemon - fsmonitor: config settings are repository-specific - help: include fsmonitor--daemon feature flag in version info - fsmonitor-ipc: create client routines for git-fsmonitor--daemon - fsmonitor--daemon: update fsmonitor documentation - fsmonitor--daemon: man page - simple-ipc: preparations for supporting binary messages. An attempt to write and ship with a watchman equivalent tailored for our use. Expecting a reroll post 2.33 release.
I have a V4 ready to send to the list. This addresses the mailing list feedback from V3 as well as feedback from git-for-windows users who have been using the experimental preview that we shipped with V2.32 and V2.33. Unfortunately, the series now contains 58 commits. I realize that this is probably way to big to send in one batch. Junio, how would you prefer that I submit this? Would you rather drop the existing series and have me send 4 or 5 parts (in a fresh series of gitgitgadget PRs) that could be reviewed in parallel and just sent to "next" in series. And then maybe they all wait in "next" until the last one is ready and all graduate to "master" together? Or would you prefer another approach? Thanks, Jeff https://github.com/gitgitgadget/git/pull/923
