git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 17, 2015, 12:00 UTC
Message-ID
<alpine.DEB.1.00.1511171253190.1686@s15462909.onlinehome-server.info>
In-Reply-To
<20151028211415.GA24501@sigill.intra.peff.net>
Hi Peff,
On Wed, 28 Oct 2015, Jeff King wrote:
Show 11 quoted lines
> On Tue, Oct 27, 2015 at 07:29:39PM -0400, Sean Krauth wrote:
> 
> > 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.

Quite possible. If the path is too long, for example, that might happen. We have support for `core.longpaths` in Git for Windows, but it will only help to a certain extent.

Show 7 quoted lines
> 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.

Actually, I would much prefer proper bug reports in the GitHub issue tracker, as described in https://git-for-windows.github.io/#contribute (in particular, I would like bug reporters to at least *skim* the guide lines https://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines; you would be surprised how many reports leave out pretty much all interesting metadata, essentially stating "something broke, somewhere", hoping that I can reproduce magically some vaguely described issue, which of course I cannot, but I still have to spend hours just to figure that out).

I would like to keep the Google Group only for Windows-specific questions that do not necessarily involve a bug in our software.

Ciao, Dscho

Previous: Jeff KingNext: Johannes Schindelin
Message 3 of 4 in “fatal: Unable to read current working directory: No error”
  1. Sean KrauthOct 27, 2015
  2. Jeff KingOct 28, 2015
  3. Johannes SchindelinNov 17, 2015
  4. Johannes SchindelinNov 17, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.