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

Bug: fsmonitor--daemon doesn't pick up submodule changes

From
BKBenedek Kozma <cyberbeni@gmail.com>
Date
May 31, 2022, 19:08 UTC
Message-ID
<CAN8jHOhn+tNn2cR7X_fPyyLF-ADiScD2gymKY9H2ZFb+UdkJSw@mail.gmail.com>

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue) git status cd submodule git checkout origin/HEAD cd .. git status

What did you expect to happen? (Expected behavior) the second git status showing that a submodule changed

What happened instead? (Actual behavior) second git status also shows up to date

What's different between what you expected and what actually happened?

Anything else you want to add: I have core.fsmonitor set to true in ~/.gitconfig If I run `git status` with git version 2.32.1 then 2.36.1 will also correctly report the submodule as changed after the next git status (because I don't have an fsmonitor script named true, using git 2.32.1 will reset my cache)

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info] git version: git version 2.36.1 cpu: arm64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Darwin 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000 arm64 compiler info: clang: 13.1.6 (clang-1316.0.21.2) libc info: no libc information available $SHELL (typically, interactive shell): /bin/zsh

[Enabled Hooks] pre-commit

Next: Johannes Schindelin
Message 1 of 3 in “Bug: fsmonitor--daemon doesn't pick up submodule changes”
  1. Benedek KozmaMay 31, 2022
  2. Johannes SchindelinJun 2, 2022
  3. Benedek KozmaJun 6, 2022

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.