Re: Committing crimes with NTFS-3G

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Aug 30, 2024, 15:02 UTC
Message-ID: <ZtHe8Vi9aRmY-UMI@tapette.crustytoothpaste.net>
In-Reply-To: <3eda2715-3b44-469e-85d5-f25504212928@gaijin.team>

On 2024-08-30 at 12:52:05, Roman Sandu wrote:

Show 9 quoted lines

> Yes, I am aware that the index will be fully refreshed on the first run of
> status. That is completely acceptable. But that is not what I am observing,
> it is being refreshed on every single run of `git status`!
> 
> After running stat before and after a status, the sha256 is identical. Both
> for files and for folders. Maybe Windows has somehow corrupted the index
> with its negative aura which makes git invalidate it on every single run?
> Are there tools in git to diagnose the reason for the index's cache being
> invalidated?

It would still be helpful to see the output of the `stat` command, since that would tell us useful things about what's causing Git to think the data has changed. For example, some systems lack certain timestamp granularity, which can break Git when compiled in certain ways.

You can see if setting `core.trustctime` to false fixes it, and you can also try `core.checkStat` to `minimal` as well. You should try them in that order to see if they fix things.

Also, what version of Git are you using? Is it the one in Ubuntu 24.04, or the one from the git-core PPA, or a different one?

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA