Welcome to the Power Users community on Codidact!
Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.
Post History
I fixed the problem by re-installing GIT. I also updated to the latest version instead of re-installing the existing version. I was running version 2.32.0-64 and am now running 2.37.2.2-64. Howe...
Answer
#1: Initial revision
by
Olin Lathrop
·
2022-08-19T17:00:20Z (about 2 years ago)
I fixed the problem by re-installing GIT. I also updated to the latest version instead of re-installing the existing version. I was running version 2.32.0-64 and am now running 2.37.2.2-64. However, the version update was unlikely the fix since the old version worked fine until a few days ago. Apparently something got wiped out that was overwritten by re-installing GIT. That fixed the problem, but is a rather unsatisfactory answer since it doesn't explain what actually happened. I still don't understand how a global GIT setting could make it not even know what the origin is in all local repositories. All 91 local repositories getting clobbered the same way is highly unlikely, and wouldn't be fixed by re-installing GIT anyway. What global setting can cause GIT to not show origin, not complain about an error, and take seconds to not do anything?