https://github.blog/open-source/git/highlights-from-git-2-37/?utm_source=chatgpt.com > In the past, Git has made it possible to integrate with tools like Watchman via a hook, making it possible to replace Git’s expensive refreshing process with a long-running daemon which tracks the filesystem state more directly. > >But setting up this hook and installing a third-party tool can be cumbersome. In Git 2.37, this functionality is built into Git itself on Windows and macOS, removing the need to install an external tool and configure the hook. Very well, on Windows and macOS we don't need `watchman` anymore. We still need it on Linux, but that simplifies things greatly. I think I came across this information ages ago, but kind of disregarded it since we still needed it for `hg`. Now that we're switching off `hg` fully to `git`, in the context of this bug, we no longer need to bundle `watchman`.
Bug 1934097 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
https://github.blog/open-source/git/highlights-from-git-2-37 > In the past, Git has made it possible to integrate with tools like Watchman via a hook, making it possible to replace Git’s expensive refreshing process with a long-running daemon which tracks the filesystem state more directly. > >But setting up this hook and installing a third-party tool can be cumbersome. In Git 2.37, this functionality is built into Git itself on Windows and macOS, removing the need to install an external tool and configure the hook. Very well, on Windows and macOS we don't need `watchman` anymore. We still need it on Linux, but that simplifies things greatly. I think I came across this information ages ago, but kind of disregarded it since we still needed it for `hg`. Now that we're switching off `hg` fully to `git`, in the context of this bug, we no longer need to bundle `watchman`.