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

why not preserve file permissions?

From
jidanni@jidanni.org <jidanni@jidanni.org>
Date
Dec 5, 2008, 20:08 UTC
Message-ID
<87tz9igzbr.fsf@jidanni.org>

Why not preserve permissions the way you find them, instead of just using 644 and 755? It certainly couldn't be more complicated than what you are doing now, and that way one could do things like use git to update system administration files across a sneakernet containing e.g., # dlocate -lsconf exim4-config|sed 's/ .*//'|sort -u -rw-r----- -rw-r--r-- -rwxr-xr-x

> git was made for tracking source code, not 640 files.
On the sneakernet no public patches would be sent, and the
administrator would remember to make the sensitive .git directories
700. And sure, git should enforce umask or no set-uid or whatever when
doing a checkout etc. The deluxe edition of git could even print a
warning: "you are trying to track a 640 file but your .git permissions
are less restrictive." However I recommend no premium or deluxe
editions for now.
> Patches welcome.

Trust me, you don't want "grandpa who forgot the parking brake" anywhere near your code.

Next: Jakub Narebski
Message 1 of 5 in “why not preserve file permissions?”
  1. jidanni@jidanni.orgDec 5, 2008
  2. Jakub NarebskiDec 5, 2008
  3. Junio C HamanoDec 5, 2008
  4. Jeff KingDec 6, 2008
  5. Daniel BarkalowDec 6, 2008

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.