Re: git > 2.10.1 fails to update index on macOS 10.14.5
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Mar 24, 2020, 23:59 UTC
- Message-ID
- <20200324235934.GI6499@camp.crustytoothpaste.net>
- In-Reply-To
- <414a10db-18d4-0c19-eafe-fbb85811fffe@smalls.rocks>
On 2020-03-24 at 01:36:18, Jonathan Smalls wrote:
Show 19 quoted lines
> > > On 3/23/20 19:13, brian m. carlson wrote: > > What exactly do you mean by "doesn't recognize any file changes"? Can > > you tell us what commands you ran and what you expected to see, and what > > you actually saw? That information would be helpful for us to track > > down what might be happening. > > In git-2.22: > > I would write a change to a file. Running `git status` would return that the > working directory was clean, and `git commit .` would show that there were > no changes to commit. > However I could target a specific file like `git commit test.txt`, and git > would successfully recognize the change, and write the commit. I could also > run `git reset --hard`, and that would update the index to reflect the > change that I had just written rather than resetting the working directory > to match the latest commit. If I ran `git reset --hard` a second time, that > command would reset the working directory.
Does running "ls -l" on the file before and after show different timestamps and file sizes? Does "git config -l | grep -iE 'checkstat|ctime'" show anything? Can you use the stat(1) command to tell us whether the change results in a device or inode number change (if that's possible using the macOS version)?
-- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204