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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Dec 23 01:38:44 2005
This archive was generated by hypermail 2.1.8 : 2005-12-23 01:38:51 EST