Hi Jeff, On Fri, 11 Feb 2022, Jeff Hostetler via GitGitGadget wrote: > Here is V5 of Part 2 of my Builtin FSMonitor series. I apologize for the > delay since V4 that I submitted back in October. (Insert the usual $DayJob > excuse...) > > I have rebased this branch onto the current "master" branch. Thank you for your tireless work on this. I do see that it requires a ton of effort on your part and just wanted to let you know that I appreciate it very much! > In this version I removed the core.useBuiltinFSMonitor config setting and > instead extended the existing core.fsmonitor. I am somewhat surprised that a reviewer suggested this, as it breaks the common paradigm we use to allow using several Git versions on the same worktree. Imagine, for example, that you run a Git version that understands `core.fsmonitor=true` to imply the built-in FSMonitor, while you _also_ use an IDE that bundles a slightly older Git version that mistakes the `true` for meaning the executable `true` (which is not a FSMonitor at all, but its exit code suggests that everything's fine and dandy). The result would be that the IDE does not see _any_ updates anymore, but nothing would suggest that anything is wrong. We can probably warn users about this, and we can also work around the fact that Git for Windows already uses `core.useBuiltinFSMonitor`, but it makes me somewhat uneasy nevertheless. Thank you, Dscho
