From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "R. David Murray" <rdmurray@bitdance.com>, git@vger.kernel.org
Subject: Re: Fatal: <hash> is corrupted can be caused by wrong permissions
Date: Sat, 25 Oct 2014 03:17:41 -0700 [thread overview]
Message-ID: <20141025101741.GA17058@peff.net> (raw)
In-Reply-To: <vpqbnp1zhp7.fsf@anie.imag.fr>
On Fri, Oct 24, 2014 at 04:05:24PM +0200, Matthieu Moy wrote:
> I can reproduce with Git 1.7.10 by doing a chmod 0 on some object files,
> but recent Git's produce
>
> Checking object directories: 100% (256/256), done.
> fatal: failed to read object ab2e06e74d922268fbff8d219dad9eee63786947: Permission denied
>
> So I guess this has already been fixed :-).
Probably d6c8a05 (open_sha1_file: report "most interesting" errno,
2014-05-15). The example in the commit message even uses "chmod 0". :)
It's in v2.0.1.
-Peff
prev parent reply other threads:[~2014-10-25 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 13:48 Fatal: <hash> is corrupted can be caused by wrong permissions R. David Murray
2014-10-24 14:05 ` Matthieu Moy
2014-10-25 10:17 ` Jeff King [this message]
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=20141025101741.GA17058@peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=rdmurray@bitdance.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).