From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jonathan Smalls <jon@smalls.rocks>
Cc: 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 23:13:51 +0000 [thread overview]
Message-ID: <20200323231351.GD6499@camp.crustytoothpaste.net> (raw)
In-Reply-To: <7b8b23f8-e12a-bde9-4b9e-ca8c908d1203@smalls.rocks>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On 2020-03-23 at 14:37:30, Jonathan Smalls wrote:
> After upgrading my work station, I found in git-2.22 that git would not
> recognize any file changes until I ran `git reset --hard`. I thought that
> it was a problem with my own settings.
> However I upgraded to git-2.25, and the problem actually got worse. In 2.25
> the index still failed to update, but `git reset --hard` no longer had any
> effect.
I have a bunch of colleagues who use the latest Git on macOS, so I
expect it does work most of the time. Let's see if we can figure out
what's going on here.
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.
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?
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-03-23 23:13 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 [this message]
2020-03-24 1:36 ` Jonathan Smalls
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=20200323231351.GD6499@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=jon@smalls.rocks \
--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).