All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Matt Schoen <mtschoen@gmail.com>
Cc: Jay Soffian <jaysoffian@gmail.com>, <git@vger.kernel.org>
Subject: Re: get git not to care about permissions
Date: Thu, 12 Nov 2009 17:10:43 +0100	[thread overview]
Message-ID: <200911121710.44314.trast@student.ethz.ch> (raw)
In-Reply-To: <3cf217d80911120744g5e020003rc00c460fff0bff1d@mail.gmail.com>

Matt Schoen wrote:
> error: Unable to open
> /ad/eng/courses/ec/ec464/ec464-team03/test.git/HEAD.lock for writing
> 
> ls -al in the directory gives me:
> total 12
> drwx------ 3 schoen root 4096 Nov 12 10:41 .
> d--------- 7 root   root 4096 Nov 12 10:41 ..
> -rwx------ 1 schoen root    0 Nov 12 10:41 HEAD.lock

At least in my current copy, this can only come from

	// lock.c:1371
	lockpath = mkpath("%s.lock", git_HEAD);
	fd = open(lockpath, O_CREAT | O_EXCL | O_WRONLY, 0666);
	if (fd < 0) {
		error("Unable to open %s for writing", lockpath);

It prints an absolute path, so the open() also accesses an absolute
path (though I don't know why it insists on that).

But the above directory listing would indicate that you do not even
have permission to look inside your $(pwd) by absolute path...

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2009-11-12 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 16:06 get git not to care about permissions sconeman
2009-11-12  5:44 ` Jay Soffian
2009-11-12 15:44   ` Matt Schoen
2009-11-12 16:10     ` Thomas Rast [this message]
2009-11-12 21:44       ` Matt Schoen
2009-11-15 12:31         ` Thomas Rast
     [not found] ` <76c5b8580911111327k43daece9s2e71d0a2b8adcebd@mail.gmail.com>
     [not found]   ` <76c5b8580911111334p76232995qbd6bf6b06d250854@mail.gmail.com>
2009-11-12 15:28     ` Eugene Sajine
2009-11-12 15:47       ` Matt Schoen

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=200911121710.44314.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    --cc=mtschoen@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.