From: Jonathan Smalls <jon@smalls.rocks>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org,
Torey Adler - NOAA Federal <torey.adler@noaa.gov>
Subject: Re: git > 2.10.1 fails to update index on macOS 10.14.5
Date: Mon, 23 Mar 2020 21:36:18 -0400 [thread overview]
Message-ID: <414a10db-18d4-0c19-eafe-fbb85811fffe@smalls.rocks> (raw)
In-Reply-To: <20200323231351.GD6499@camp.crustytoothpaste.net>
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.
In normal operation, I would expect to `git status` to recognize a
change in a file once it had already been added to the index. I would
expect `git commit .` to commit all files in the current directory, and
subdirectories without having to specify their file names. I would
expect `git reset --hard` to revert the working directory to match the
latest commit the first time.
In git-2.25
I would write a change to a file. `git status` would continue to show
that the working directory was clean, but I was not longer able to
target a particular file to force a commit. `git reset --hard` had no
effect, and still showed that the working directory was clean without
resetting the working directory.
To successfully commit a file I would have to run `git rm --cached
test.txt` to target a file, and then `git add test.txt` for git to
update its index, and recognize the change.
I would expect the same normal operation in git-2.25.
>
> Also, are you using any specific workflow or tool that might be related?
> Are you using an editor integration or GUI, and if so, does this happen
> without that editor integration or GUI as well?
I use git on the command line, so there should be no external
interference with its normal function.
next prev parent reply other threads:[~2020-03-24 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:37 git > 2.10.1 fails to update index on macOS 10.14.5 Jonathan Smalls
2020-03-23 23:13 ` brian m. carlson
2020-03-24 1:36 ` Jonathan Smalls [this message]
2020-03-24 23:59 ` brian m. carlson
2020-03-30 11:20 ` Jonathan Smalls
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=414a10db-18d4-0c19-eafe-fbb85811fffe@smalls.rocks \
--to=jon@smalls.rocks \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=torey.adler@noaa.gov \
/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).