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

git-clone ignores umask for working tree

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jul 6, 2012, 19:27 UTC
Message-ID
<CALxABCZn5W-cEQ9PS+4XoqhH7L+5P3KN==_RrcruK+oKdijmWw@mail.gmail.com>
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?
This Stackoverflow question is what got me interested:
http://stackoverflow.com/questions/10637416/git-clone-respects-umask-except-for-top-level-project-directory
and might provide a credible use case.

Regards, Alex

Next: Daniel Barkalow
Message 1 of 10 in “git-clone ignores umask for working tree”
  1. Alex RiesenJul 6, 2012
  2. Daniel BarkalowJul 6, 2012
  3. Restore umasks influence on the permissions of work tree created by cloneAlex Riesen, Jul 7, 2012
  4. Junio C HamanoJul 9, 2012
  5. Alex RiesenJul 9, 2012
  6. Jeff KingJul 9, 2012
  7. Junio C HamanoJul 9, 2012
  8. Junio C HamanoJul 9, 2012
  9. rerere: make rr-cache fanout directory honor umaskJunio C Hamano, Jul 9, 2012
  10. Jeff KingJul 10, 2012

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.