git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Sean Krauth <spkrauth@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: fatal: Unable to read current working directory: No error
Date: Wed, 28 Oct 2015 17:14:15 -0400	[thread overview]
Message-ID: <20151028211415.GA24501@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPkB0GxPghR9Y7YrB9yYq3rA9XZ2HJGN-sxbQgERGsBA2iOX_Q@mail.gmail.com>

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. 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

  reply	other threads:[~2015-10-28 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 23:29 fatal: Unable to read current working directory: No error Sean Krauth
2015-10-28 21:14 ` Jeff King [this message]
2015-11-17 12:00   ` Johannes Schindelin
2015-11-17 11:52 ` Johannes Schindelin

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151028211415.GA24501@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=spkrauth@gmail.com \
    /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.
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 NNTP newsgroup(s).