{"thread":{"id":"40661","subject":"fatal: Unable to read current working directory: No error","startedAt":"2015-10-27T23:29:39Z","lastAt":"2015-11-17T12:00:17Z","messageCount":4,"participants":["Sean Krauth","Jeff King","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"272360","messageId":"CAPkB0GxPghR9Y7YrB9yYq3rA9XZ2HJGN-sxbQgERGsBA2iOX_Q@mail.gmail.com","threadId":"40661","inReplyTo":null,"subject":"fatal: Unable to read current working directory: No error","fromName":"Sean Krauth","fromEmail":"spkrauth@gmail.com","sentAt":"2015-10-27T23:29:39Z","receivedAt":"2015-10-27T23:29:39Z","isPatch":false,"sender":{"key":"spkrauth@gmail.com","avatar":null},"body":"Dear magic git bug solver,\n\nI've encountered a problem and I haven't had any success with my own\ntroubleshooting or googling so I'd appreciate some help. I noticed the\nissue originally when I changed a file name in windows explorer. I was\nworking on a website and I named my Public folder with a capital P and\nwrote my file routes as public. So being a little lazy I decided to\nopen windows explorer and rename Public to public. This was after I\nhad used Git Bash to create a local repository. I'm almost positive\nthis action broke Git. The next time I tried to run Git Bash I got an\nerror that I believe said something similar to \"fatal build error\" or\n\"fatal load error\" and Git was really broke.\n\nThis seemed like about as good of an excuse as any to update Git. I\nwas running v. 2.5.1-32-bit and so I downloaded v. 2.6.2-32-bit,\ninstalled it. And it ran, kinda. I no longer seem to have access to\nany of my old commits and when I try to \"git init\" or \"git status\" I\nget the above error, \"fatal: Unable to read current working directory:\nNo error\". This error pops up for anything, even new files that never\nhad a repository.\n\nI'm sorry if this wasn't very well documented or explained, but it\nkinda caught me off guard. Any thoughts or possible solutions on how\nto get Git running again would be greatly appreciated.\n\nSincerely,\nSean Krauth\n"},{"id":"272437","messageId":"20151028211415.GA24501@sigill.intra.peff.net","threadId":"40661","inReplyTo":"CAPkB0GxPghR9Y7YrB9yYq3rA9XZ2HJGN-sxbQgERGsBA2iOX_Q@mail.gmail.com","subject":"Re: fatal: Unable to read current working directory: No error","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2015-10-28T21:14:15Z","receivedAt":"2015-10-28T21:14:15Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Oct 27, 2015 at 07:29:39PM -0400, Sean Krauth wrote:\n\n> This seemed like about as good of an excuse as any to update Git. I\n> was running v. 2.5.1-32-bit and so I downloaded v. 2.6.2-32-bit,\n> installed it. And it ran, kinda. I no longer seem to have access to\n> any of my old commits and when I try to \"git init\" or \"git status\" I\n> get the above error, \"fatal: Unable to read current working directory:\n> No error\". This error pops up for anything, even new files that never\n> had a repository.\n\nThat message means that getcwd() is failing. If it were happening in one\nplace, I'd say to check if there is something funny with your directory\n(e.g., bad permissions or something). But if it's happening anywhere, it\nsounds like there is some fundamental incompatibility between the build\nof Git and your system.\n\nIt sounds like you're on a Windows system, and the problem may be\nsystem-specific. You might try asking at the specific Git for Windows\nlist:\n\n  https://groups.google.com/forum/?hl=en#!forum/git-for-windows\n\nthough many of those people do frequent this list, too.\n\n-Peff\n"},{"id":"273428","messageId":"alpine.DEB.1.00.1511171251120.1686@s15462909.onlinehome-server.info","threadId":"40661","inReplyTo":"CAPkB0GxPghR9Y7YrB9yYq3rA9XZ2HJGN-sxbQgERGsBA2iOX_Q@mail.gmail.com","subject":"Re: fatal: Unable to read current working directory: No error","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2015-11-17T11:52:57Z","receivedAt":"2015-11-17T11:52:57Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Sean,\n\nOn Tue, 27 Oct 2015, Sean Krauth wrote:\n\n> I've encountered a problem and I haven't had any success with my own\n> troubleshooting or googling so I'd appreciate some help. I noticed the\n> issue originally when I changed a file name in windows explorer. I was\n> working on a website and I named my Public folder with a capital P and\n> wrote my file routes as public. So being a little lazy I decided to\n> open windows explorer and rename Public to public. This was after I\n> had used Git Bash to create a local repository. I'm almost positive\n> this action broke Git. The next time I tried to run Git Bash I got an\n> error that I believe said something similar to \"fatal build error\" or\n> \"fatal load error\" and Git was really broke.\n\nIf you could boil this down to a [Minimal, Complete & Verifiable\nExample](http://stackoverflow.com/help/mcve), I will have a look.\n\nCiao,\nJohannes\n"},{"id":"273429","messageId":"alpine.DEB.1.00.1511171253190.1686@s15462909.onlinehome-server.info","threadId":"40661","inReplyTo":"20151028211415.GA24501@sigill.intra.peff.net","subject":"Re: fatal: Unable to read current working directory: No error","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2015-11-17T12:00:17Z","receivedAt":"2015-11-17T12:00:17Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Peff,\n\nOn Wed, 28 Oct 2015, Jeff King wrote:\n\n> On Tue, Oct 27, 2015 at 07:29:39PM -0400, Sean Krauth wrote:\n> \n> > This seemed like about as good of an excuse as any to update Git. I\n> > was running v. 2.5.1-32-bit and so I downloaded v. 2.6.2-32-bit,\n> > installed it. And it ran, kinda. I no longer seem to have access to\n> > any of my old commits and when I try to \"git init\" or \"git status\" I\n> > get the above error, \"fatal: Unable to read current working directory:\n> > No error\". This error pops up for anything, even new files that never\n> > had a repository.\n> \n> That message means that getcwd() is failing.\n\nQuite possible. If the path is too long, for example, that might happen.\nWe have support for `core.longpaths` in Git for Windows, but it will only\nhelp to a certain extent.\n\n> It sounds like you're on a Windows system, and the problem may be\n> system-specific. You might try asking at the specific Git for Windows\n> list:\n> \n>   https://groups.google.com/forum/?hl=en#!forum/git-for-windows\n> \n> though many of those people do frequent this list, too.\n\nActually, I would much prefer proper bug reports in the GitHub issue\ntracker, as described in https://git-for-windows.github.io/#contribute (in\nparticular, I would like bug reporters to at least *skim* the guide lines\nhttps://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines;\nyou would be surprised how many reports leave out pretty much all\ninteresting metadata, essentially stating \"something broke, somewhere\",\nhoping that I can reproduce magically some vaguely described issue, which\nof course I cannot, but I still have to spend hours just to figure that\nout).\n\nI would like to keep the Google Group only for Windows-specific questions\nthat do not necessarily involve a bug in our software.\n\nCiao,\nDscho\n"}]}