git/list[1] front-page[2] threads[3] people[4] search[5] about
 

core.fsmonitor always perform rescans

From
TITatsuyuki Ishi <ishitatsuyuki@gmail.com>
Date
Mar 26, 2018, 04:41 UTC
Message-ID
<CANqewP332-+esYWDPBtPif==wnb4PiNd89R1qTZsuWZAFSV0ew@mail.gmail.com>
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 has crawled the directories, watchman will always return all files inside the directory. This happens everytime I run a git command, resulting in slowness.

Is the timestamp not being updated an intended behavior, or is this a bug?
Tatsuyuki Ishi
Next: Johannes Schindelin
Message 1 of 4 in “core.fsmonitor always perform rescans”
  1. Tatsuyuki IshiMar 26, 2018
  2. Johannes SchindelinMar 30, 2018
  3. Ben PeartApr 10, 2018
  4. Tatsuyuki IshiApr 11, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.