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

Re: [EXTERNAL] Re: BUG: git clean -d cannot remove files from read-only directories

From
Jeff King <peff@peff.net>
Date
Feb 21, 2020, 05:38 UTC
Message-ID
<20200221053838.GD1280313@coredump.intra.peff.net>
In-Reply-To
<BL0PR2101MB1089E6E522A983429473719380120@BL0PR2101MB1089.namprd21.prod.outlook.com>
On Fri, Feb 21, 2020 at 03:06:13AM +0000, Adam Milazzo wrote:
> I wonder now why Git makes an effort of appearing to represent a full
> set of Unix file permissions. Perhaps the idea was to leave the door
> open to storing them in the future...

I think to some degree it's the other way around. The very earliest versions of Git did track the full mode, but that turned out to be annoying (you'd record useless changes caused by umasks of different committers). It was changed in e44794706e (Be much more liberal about the file mode bits., 2005-04-16), which is quite early on. :)

We do use the mode bits for other things, too. Subtrees are 040000, symlinks are 120000, and submodule "gitlinks" are 160000.

-Peff
Previous: Adam Milazzo
Message 4 of 4 in “Re: BUG: git clean -d cannot remove files from read-only directories”
  1. Adam MilazzoFeb 21, 2020
  2. Elijah NewrenFeb 21, 2020
  3. Adam MilazzoFeb 21, 2020
  4. Jeff KingFeb 21, 2020

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.