git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Benedek Kozma <cyberbeni@gmail.com>
To: git@vger.kernel.org
Subject: Bug: fsmonitor--daemon doesn't pick up submodule changes
Date: Tue, 31 May 2022 21:08:38 +0200	[thread overview]
Message-ID: <CAN8jHOhn+tNn2cR7X_fPyyLF-ADiScD2gymKY9H2ZFb+UdkJSw@mail.gmail.com> (raw)

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

             reply	other threads:[~2022-05-31 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 19:08 Benedek Kozma [this message]
2022-06-02 13:28 ` Bug: fsmonitor--daemon doesn't pick up submodule changes Johannes Schindelin
2022-06-06 10:46   ` Benedek Kozma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN8jHOhn+tNn2cR7X_fPyyLF-ADiScD2gymKY9H2ZFb+UdkJSw@mail.gmail.com \
    --to=cyberbeni@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).