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

working directory umask

From
DHD Herring <dherring@tentpost.com>
Date
Feb 2, 2010, 06:30 UTC
Message-ID
<hk8gq7$o76$1@ger.gmane.org>
Hi all,

So for one project at work, we have a (slow) server with a common build area. Standard practice has been to extract a tarball, configure, make, make install into a common area. I have started using git to replace the tarballs -- keep version info, make doesn't have to rebuild everything, auto-tag install sources, etc.

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...

Is there an option that I've overlooked? I can't seem to find anything that overrides umask in the working directory, only in the repo.

Thanks, Daniel

Next: Junio C Hamano
Message 1 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.