Re: git /objects directory created 755 by default?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Dec 21, 2005, 22:20 UTC
Message-ID: <Pine.LNX.4.63.0512212317400.18684@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vek465cev.fsf@assigned-by-dhcp.cox.net>

Hi,

On Wed, 21 Dec 2005, Junio C Hamano wrote:

Show 14 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > If you don't use git-shell, because the same machine is used for other 
> > purposes, it makes sense to introduce
> >
> > 	[core]
> > 		umask = 0002
> 
> I agree the setting should not be limited to git-shell, but I do
> not think setting "umask" from git configuration is the right
> way either.  For files and directories under $GIT_DIR, maybe
> imposing the policy git configuration file has is OK, but I
> think honoring the user's umask is the right thing for working
> tree files.

As we worked out in another thread, you should not have a working directory when you write-share the repository.

So, I tend to say: use core.umask only in shared setups (in which you should not checkout files unless you know exactly what you are doing).

Hmm? (I mean to imitate Linus here, not refer to hidden Markov models.)

Ciao, Dscho