From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] shared repository settings enhancement.
Date: Fri, 9 Jun 2006 21:08:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606092103170.5498@g5.osdl.org> (raw)
In-Reply-To: <7v8xo5lleo.fsf@assigned-by-dhcp.cox.net>
On Fri, 9 Jun 2006, Junio C Hamano wrote:
>
> 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
next prev parent reply other threads:[~2006-06-10 4:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 20:52 Git-daemon messing up permissions for gitweb Post, Mark K
2006-06-09 21:06 ` Junio C Hamano
2006-06-10 0:35 ` [PATCH/RFC] Retire SIMPLE_*** stuff Junio C Hamano
2006-06-10 14:13 ` [PATCH] Built-in git-get-tar-commit-id (was: [PATCH/RFC] Retire SIMPLE_*** stuff.) Rene Scharfe
2006-06-10 0:39 ` [PATCH] shared repository settings enhancement Junio C Hamano
2006-06-10 0:46 ` Linus Torvalds
2006-06-10 1:38 ` Jakub Narebski
2006-06-10 3:49 ` Junio C Hamano
2006-06-10 4:08 ` Linus Torvalds [this message]
2006-06-10 4:19 ` Junio C Hamano
2006-06-10 4:39 ` Linus Torvalds
2006-06-10 21:30 ` Git-daemon messing up permissions for gitweb Alex Riesen
2006-06-10 21:41 ` Linus Torvalds
2006-06-10 22:30 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 17:32 [PATCH] shared repository settings enhancement Post, Mark K
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.0606092103170.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).