From: Alex Riesen <raa.lkml@gmail.com>
Date: Thu, 22 Dec 2005 14:38:08 GMT
Subject: Re: git /objects directory created 755 by default?
Message-ID: <81b0412b0512220638j382252b5l24e1c6b261165bd6@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.63.0512221227190.7112@wbgn013.biozentrum.uni-wuerzburg.de>

On 12/22/05, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > > >
> > > > >     [core]
> > > > >             umask = 0002
> > > 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).
> >
> > May be "shell.umask" or "shared.umask" ?
>
> What would shell.umask do? Be set only when git-shell is called? Then you
> better have the policy to access that particular repository *only* via
> git-shell. Voila, it is the same effect as of core.umask.

I mean it to be set only when git-shell called, but with explicit semantics
("for git-shell only").

> What would shared.umask do? Be set only when writing to GIT_DIR? This is a
> major task, since you have to find out which writes are to the working
> directory, which ones go to GIT_DIR.

shared.mask = shell.mask. Just a name to express what it is for