public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha•warpmail.net>
To: git_user101 <m.aqadjanimemar@student•ru.nl>
Cc: git@vger•kernel.org
Subject: Re: Error: Unable to append to logs/HEAD: Permission denied
Date: Mon, 17 May 2010 14:26:00 +0200	[thread overview]
Message-ID: <4BF135D8.70106@drmicha.warpmail.net> (raw)
In-Reply-To: <1274098383422-5064764.post@n2.nabble.com>

git_user101 venit, vidit, dixit 17.05.2010 14:13:
> 
> Thank you, Michael!
> I do not understand what you exactly mean with "Also, you'll have to fix-up
> permissions manually at least
> on logs/HEAD (and probably others)"
> If you mean that I have to change the permission of logs/HEAD to read, write
> for the group,

I meant all files & dirs under ${repo}.git should be owned by the group
and +rw for the group. ["All" is actually overkill but sufficient.]

> it is already done.
> All files and directories in the repository are accessible for the group.

Hmm. If really all files and dirs (!) are group writeable I'm puzzled.
What is the complete report and error message (besides failed to push)?

A push can also fail due to non fast-forward, of course.

Michael

  reply	other threads:[~2010-05-17 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-16 23:18 Error: Unable to append to logs/HEAD: Permission denied git_user101
2010-05-17  7:54 ` Michael J Gruber
2010-05-17  8:17   ` git_user101
2010-05-17  9:02     ` Michael J Gruber
2010-05-17 11:09       ` git_user101
2010-05-17 11:40         ` Michael J Gruber
2010-05-17 12:13           ` git_user101
2010-05-17 12:26             ` Michael J Gruber [this message]
2010-05-17 12:48               ` git_user101
2010-05-17 13:35                 ` Michael J Gruber
2010-05-17 19:02                   ` git_user101

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=4BF135D8.70106@drmicha.warpmail.net \
    --to=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=m.aqadjanimemar@student$(echo .)ru.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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