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

git-pasky file mode handling

From
RKRussell King <rmk@arm.linux.org.uk>
Date
Apr 16, 2005, 09:45 UTC
Message-ID
<20050416104559.A12943@flint.arm.linux.org.uk>
Hi,

It seems that there's something weird going on with the file mode handling. Firstly, some files in the git-pasky repository have mode 0664 while others have 0644.

Having pulled from git-pasky a number of times, with Petr's being the "tracked" repository, I now find that when I do an update-cache --refresh, it complains that the files need updating, despite show-diff showing no differences. Investigating, this appears to be because the file modes are wrong for a number of the files. All my files do not have group write.

I notice in the changelog what appears to be a dependence on the umask. If this is so, please note that git appears to track the file modes, and any dependence upon the umask is likely to screw with this tracking.

-- 
Russell King
Next: Petr Baudis
Message 1 of 2 in “git-pasky file mode handling”
  1. Russell KingApr 16, 2005
  2. Petr BaudisApr 16, 2005

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.