RE: [PATCH] shared repository settings enhancement.

From: Post, Mark K <mark.post@eds.com>
Date: Jun 11, 2006, 17:32 UTC
Message-ID: <5A14AF34CFF8AD44A44891F7C9FF4105079578F3@usahm236.amer.corp.eds.com>

Speaking as a non-developer sysadmin, if I were to make a suggestion, it
would be this:
  [core]
     sharedrepository = {useumask | useronly | userandgroup |
worldreadable}

Mark Post

-----Original Message-----
From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On
Behalf Of Linus Torvalds
Sent: Saturday, June 10, 2006 12:09 AM
To: Junio C Hamano
Cc: git@vger.kernel.org
Subject: Re: [PATCH] shared repository settings enhancement.

On Fri, 9 Jun 2006, Junio C Hamano wrote:

Show 5 quoted lines

> 
> Having said that, I do not think the distinction is that
> important; I would rather make the core.sharedrepository = true
> to mean an equivalent of "chmod go+rX" (it does "chmod g+rX"
> currently).

How about making it be

	[core]
		sharedrepository = {umask | user | group | everybody}

and allow the old boolean expression syntax to mean "0/false means umask, 1/true means group".

So you'd have:

 - umask/0/false means "use 0777 permissions with default umask"
 - user means "use 0500 permissions"
 - group means "use 0550 permissions"
 - everybody means "use 0555 permissions"

(where "5" is r-x, and only for directories, and obviously degenerates to just "4" aka r-- for regular files).

That sounds really pretty self-explanatory and obvious, wouldn't you say?

			Linus