Thanks to Chris for the explanation and links to look around.
TL;DR
One can safely use the command git config --global core.fsmonitor true to get rid of the message for good.
The answer to the what is in Chris’s answer and to why is below.
- Seems like both of them are interconnected and hence they haven’t yet disabled one.
The new FSMonitor feature is controlled by the core.useBuiltinFSMonitor boolean.
Link
- In a recent post they seemed to have addressed this issue.
So I understand that the builtin FS monitor is not actually deprecated, just that the name in the config is going to change, is there, on the current version, any way to use the new name or is the only way to get rid of the message to disable it via the provided command?
I guess we should clarify by saying core.useBuiltinFSMonitor=true was experimental, please set core.fsmonitor=true` instead.
Link
- And finnaly, the reason for the prompt:
With the feature going upstream into core Git, a decision was made to overload the existing core.fsmonitor setting to take a hook-pathname or a boolean value for the builtin FSMonitor. However, users may have multiple versions of Git installed on their systems on Windows. One in the C:/program files/… and hidden versions installed by tools like Visual Studio. And these may be at different revision levels, so one install might only understand the old keyword and one version might understand both (during the transition). So, auto transitioning it would break whichever one is the older release. So it’s safer to just warn the user and let them decide. (And if they know they have multiple versions, they can just set both for now.)
Link