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

Re: [PATCH] Restore umasks influence on the permissions of work tree created by clone

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 9, 2012, 23:07 UTC
Message-ID
<7v1ukkjzyz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120709225829.GA8397@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Does the mkdir of "rr-cache/*" in rerere.c make the same mistake? The
> rr-cache root is made with 0777, and the files inside each subdirectory
> are created with 0666.  So it is the only thing preventing users of
> shared repos from using rerere.

Quite possibly yes. I do not recall tightening permissions on purpose, and it was a long time ago ;-)

Previous: Jeff KingNext: Junio C Hamano
Message 7 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.