Re: git-clone ignores umask for working tree
- From
Daniel Barkalow <barkalow@iabervon.org>
- Date
- Jul 6, 2012, 21:20 UTC
- Message-ID
- <alpine.LNX.2.00.1207061700060.2056@iabervon.org>
- In-Reply-To
- <CALxABCZn5W-cEQ9PS+4XoqhH7L+5P3KN==_RrcruK+oKdijmWw@mail.gmail.com>
On Fri, 6 Jul 2012, Alex Riesen wrote:
Show 7 quoted lines
> Hi list, > > when git-clone was built in, its treatment of umask has changed: the shell > version respected umask for newly created directories by using plain mkdir(1), > and the builtin version just uses mkdir(work_tree, 0755). > > Is it intentional?
I have the vague feeling that it was intentional, but it's entirely plausible that I just overlooked that mkdir(2) applies umask and went for the mode that you normally want. I don't think there's any particular need for this operation to be more restrictive than umask.
-Daniel *This .sig left intentionally blank*