git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: working directory umask

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 2, 2010, 06:43 UTC
Message-ID
<7v8wbccf3x.fsf@alter.siamese.dyndns.org>
In-Reply-To
<hk8gq7$o76$1@ger.gmane.org>
D Herring <dherring@tentpost.com> writes:
> One problem:  Even though the working directory is g+swx and git was
> initialized with --shared=group or --shared=0660, the checked out
> source files still don't have group write permissions...

It is working as designed. "shared" setting is about a shared central repository that is typically a bare repository, and currently it is implemented as such.

You could argue that the behaviour for the work tree files is undefined and make the code act differently, though.

In any case, it would be better to document this, and it might even make sense to issue a warning message when we detect the repository is used with a work tree (including the use of GIT_DIR and GIT_WORK_TREE environment variables to temporarily turn a bare repository with a work tree).

Thanks for a report.
Previous: D Herring
Message 2 of 2 in “working directory umask”
  1. D HerringFeb 2, 2010
  2. Junio C HamanoFeb 2, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.