Kevin Willford 8da2c57629 fsmonitor: handle version 2 of the hooks that will use opaque token ... Some file monitors like watchman will use something other than a timestamp to keep better track of what changes happen in between calls to query the fsmonitor. The clockid in watchman is a string. Now that the index is storing an opaque token for the last update the code needs to be updated to pass that opaque token to a verion 2 of the fsmonitor hook. Because there are repos that already have version 1 of the hook and we want them to continue to work when git is updated, we need to handle both version 1 and version 2 of the hook. In order to do that a config value is being added core.fsmonitorHookVersion to force what version of the hook should be used. When this is not set it will default to -1 and then the code will attempt to call version 2 of the hook first. If that fails it will fallback to trying version 1. Signed-off-by: Kevin Willford <Kevin.Willford@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>		2020-01-13 14:58:43 -08:00
..
fsmonitor-all	fsmonitor: handle version 2 of the hooks that will use opaque token	2020-01-13 14:58:43 -08:00
fsmonitor-env	fsmonitor: don't fill bitmap with entries to be removed	2019-10-12 10:16:11 +09:00
fsmonitor-none
fsmonitor-watchman	fsmonitor: handle version 2 of the hooks that will use opaque token	2020-01-13 14:58:43 -08:00