2018-04-10 23:34 GMT+09:00 Ben Peart :
> As a performance optimization, the fsmonitor code doesn't flag the index as
> dirty and force it to be written out with every command. Can you try
> performing a git operation (add, rm, commit, etc) that will write out an
> updated index and see if that fix
On 3/26/2018 12:41 AM, Tatsuyuki Ishi wrote:
Hello,
I'm facing issue with core.fsmonitor.
I'm currently using the provided watchman hook, but it doesn't seem to
record the fact that it has queried the fsmonitor backend, and as a
result the timestamp passed to the hook doesn't seem to change.
Hi,
On Mon, 26 Mar 2018, Tatsuyuki Ishi wrote:
> I'm facing issue with core.fsmonitor.
>
> I'm currently using the provided watchman hook, but it doesn't seem to
> record the fact that it has queried the fsmonitor backend, and as a
> result the timestamp passed to the hook doesn't seem to change
Hello,
I'm facing issue with core.fsmonitor.
I'm currently using the provided watchman hook, but it doesn't seem to
record the fact that it has queried the fsmonitor backend, and as a
result the timestamp passed to the hook doesn't seem to change.
As it always pass a timestamp before watchman ha
4 matches
Mail list logo