From: Jeff King <peff@peff.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: git@vger.kernel.org
Subject: Re: error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
Date: Wed, 29 Apr 2009 04:06:50 -0400 [thread overview]
Message-ID: <20090429080650.GA25227@coredump.intra.peff.net> (raw)
In-Reply-To: <20090429073256.GB22129@elte.hu>
On Wed, Apr 29, 2009 at 09:32:56AM +0200, Ingo Molnar wrote:
> > So I think we would need to simulate the errno setting, like the
> > patch below. That should generate the hint only when it would
> > actually be useful.
>
> it wasnt hard to figure out what's going on. So this was more of a
> FYI, not really a bug report. Maybe if someone tries to pull into a
> read-only repo the same could happen? My particular breakage (of a
> single ref being root-owned - the rest was mingo owned) is atypical
> enough to be ignored.
Actually, it is a little bit tough to get your breakage. A pure
read-only repo would error out much earlier (permission denied on
FETCH_HEAD or writing to object db). But if yours was just "accidentally
fetched once as root", then that doesn't seem too uncommon.
> If there's no easy/clean solution then please ignore my report.
I think the patch I posted isn't too bad. We'll see what others say.
-Peff
next prev parent reply other threads:[~2009-04-29 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 7:31 error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied Ingo Molnar
2009-04-29 3:29 ` Jeff King
2009-04-29 4:07 ` Jeff King
2009-04-29 7:32 ` Ingo Molnar
2009-04-29 8:06 ` Jeff King [this message]
2009-05-25 10:37 ` [PATCH 1/2] lock_ref: inform callers of unavailable ref Jeff King
2009-05-25 10:40 ` [PATCH 2/2] fetch: report ref storage DF errors more accurately Jeff King
2009-05-25 22:23 ` Junio C Hamano
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=20090429080650.GA25227@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/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).