From: Ingo Molnar <mingo@elte.hu>
To: git@vger.kernel.org
Subject: error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
Date: Tue, 28 Apr 2009 09:31:38 +0200 [thread overview]
Message-ID: <20090428073138.GA9094@elte.hu> (raw)
I had a portion of a repo owned by root accidentally, and the next
time i pulled as user mingo Git gave me this warning and suggestion:
aldebaran:~/git> git pull
error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
From e2:git
! 66996ec..95110d7 master -> origin/master (unable to update local ref)
* [new tag] v1.6.3-rc2 -> v1.6.3-rc2
error: some local refs could not be updated; try running
'git remote prune origin' to remove any old, conflicting branches
Obviousy Git cannot update the ref there so the failure is OK, but
the git-remote advice it gives is confusing IMHO: the 'git remote
prune origin' cannot fix anything. (and it is clear from the fetch
permission failure that there's no chance to fix anything here.)
I suspect there are other, more typical failure modes where that
advice is useful - just wanted to point out that it's confusing
here.
Ingo
next reply other threads:[~2009-04-28 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 7:31 Ingo Molnar [this message]
2009-04-29 3:29 ` error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied Jeff King
2009-04-29 4:07 ` Jeff King
2009-04-29 7:32 ` Ingo Molnar
2009-04-29 8:06 ` Jeff King
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=20090428073138.GA9094@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
/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).