git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: "Post, Mark K" <mark.post@eds.com>
Cc: git@vger.kernel.org
Subject: Re: Git-daemon messing up permissions for gitweb
Date: Fri, 9 Jun 2006 12:05:36 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606091201210.5498@g5.osdl.org> (raw)
In-Reply-To: <5A14AF34CFF8AD44A44891F7C9FF41050795782F@usahm236.amer.corp.eds.com>



On Fri, 9 Jun 2006, Post, Mark K wrote:
>
> As far as I can tell, the problem is happening because these files are
> being written out with file permissions of 640, and since Apache is
> running as user wwwrun, it can't read them:

You can either make sure that people have something like

	umask 0022

in their bashrc (or that it's the default umask), so that they do things 
world-readably by default.

Or add
	[core]
		SharedRepository = true

to the repository config file.

		Linus

  parent reply	other threads:[~2006-06-09 19:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 18:41 Git-daemon messing up permissions for gitweb Post, Mark K
2006-06-09 18:58 ` Jakub Narebski
2006-06-09 19:05 ` Linus Torvalds [this message]
2006-06-09 20:01   ` Junio C Hamano
2006-06-09 19:51 ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2006-06-09 19:11 Post, Mark K
2006-06-09 19:27 ` Jakub Narebski
2006-06-09 20:08 Post, Mark K
2006-06-09 20:18 ` Junio C Hamano
2006-06-09 20:22 ` Linus Torvalds
2006-06-09 20:34   ` Junio C Hamano
2006-06-09 20:44     ` Linus Torvalds
2006-06-09 21:02       ` Jakub Narebski
2006-06-09 20:29 Post, Mark K
2006-06-09 20:45 Post, Mark K
2006-06-09 20:52 Post, Mark K
2006-06-09 21:06 ` Junio C Hamano
2006-06-10 21:30 ` Alex Riesen
2006-06-10 21:41   ` Linus Torvalds
2006-06-10 22:30     ` Alex Riesen

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=Pine.LNX.4.64.0606091201210.5498@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=mark.post@eds.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).