Re: fatal: Unable to read current working directory: No error

From: Jeff King <peff@peff.net>
Date: Oct 28, 2015, 21:14 UTC
Message-ID: <20151028211415.GA24501@sigill.intra.peff.net>
In-Reply-To: <CAPkB0GxPghR9Y7YrB9yYq3rA9XZ2HJGN-sxbQgERGsBA2iOX_Q@mail.gmail.com>

On Tue, Oct 27, 2015 at 07:29:39PM -0400, Sean Krauth wrote:

Show 7 quoted lines

> This seemed like about as good of an excuse as any to update Git. I
> was running v. 2.5.1-32-bit and so I downloaded v. 2.6.2-32-bit,
> installed it. And it ran, kinda. I no longer seem to have access to
> any of my old commits and when I try to "git init" or "git status" I
> get the above error, "fatal: Unable to read current working directory:
> No error". This error pops up for anything, even new files that never
> had a repository.

That message means that getcwd() is failing. If it were happening in one place, I'd say to check if there is something funny with your directory (e.g., bad permissions or something). But if it's happening anywhere, it sounds like there is some fundamental incompatibility between the build of Git and your system.

It sounds like you're on a Windows system, and the problem may be system-specific. You might try asking at the specific Git for Windows list:

  https://groups.google.com/forum/?hl=en#!forum/git-for-windows

though many of those people do frequent this list, too.

-Peff