"Kevin Willford via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > When running Git commands quickly -- such as in a shell script or the test > suite -- the Git commands frequently complete and start again during the > same second. The example fsmonitor hooks to integrate with Watchman truncate > the nanosecond times to seconds. In principle, this is fine, as Watchman > claims to use inclusive comparisons [1]. The result should only be an > over-representation of the changed paths since the last Git command. > ... So, it doesn't seem to use "inclusive" and we need a workaround? > Kevin Willford (1): > fsmonitor: fix watchman integration > > t/t7519/fsmonitor-watchman | 13 ++++--------- > templates/hooks--fsmonitor-watchman.sample | 13 ++++--------- > 2 files changed, 8 insertions(+), 18 deletions(-) Thanks, will queue.
