From: Heikki Orsila <shdl@zakalwe.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add two core.sharedRepository options: group-readable and world-readable
Date: Sat, 12 Apr 2008 15:01:59 +0300 [thread overview]
Message-ID: <20080412120159.GC31039@zakalwe.fi> (raw)
In-Reply-To: <7vzlrzlluj.fsf@gitster.siamese.dyndns.org>
On Fri, Apr 11, 2008 at 09:48:36PM -0700, Junio C Hamano wrote:
> Heikki Orsila <shdl@zakalwe.fi> writes:
>
> > On Fri, Apr 11, 2008 at 05:53:36PM -0700, Junio C Hamano wrote:
> > ...
> >> For example, you may want to enforce "ug+rw,o=" in a repository. How
> >> would you do that?
> >
> > Isn't that PERM_GROUP? The user always keeps u+rw for oneself.
>
> My question was about the "o=" part. I did not see you dropping bits for
> others in your patch.
>
> And if your answer is "the user should have xx7 umask", that defeats the
> whole point of your patch, as you are trying to dissociate the umask used
> by the user for his usual task and enforce particular permission policy
> for the repository.
You're correct. There are two options, do you have a preference on this
matter?
1. current method + mask off others when needed
2. core.sharedRepository=0xxx
I think I like option 2 better (preserving backwards compatibility of
course).
--
Heikki Orsila Barbie's law:
heikki.orsila@iki.fi "Math is hard, let's go shopping!"
http://www.iki.fi/shd
next prev parent reply other threads:[~2008-04-12 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 14:09 [PATCH] Add two core.sharedRepository options: group-readable and world-readable Heikki Orsila
2008-04-12 0:53 ` Junio C Hamano
2008-04-12 3:00 ` Heikki Orsila
2008-04-12 4:48 ` Junio C Hamano
2008-04-12 9:17 ` Björn Steinbrink
2008-04-12 10:03 ` Junio C Hamano
2008-04-12 18:52 ` Heikki Orsila
2008-04-12 12:01 ` Heikki Orsila [this message]
2008-04-12 12:05 ` Heikki Orsila
-- strict thread matches above, loose matches on Subject: below --
2008-04-11 14:41 Heikki Orsila
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=20080412120159.GC31039@zakalwe.fi \
--to=shdl@zakalwe.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).