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

Re: How can I force git to recognize a change change in file modes?

From
Jan Krüger <jk@jk.gs>
Date
Feb 28, 2009, 03:55 UTC
Message-ID
<20090228045531.14399ebf@perceptron>
In-Reply-To
<e38bce640902271717s46cf47f9i7c6bf5aac0d5f273@mail.gmail.com>
Hi,
Show 6 quoted lines
> I checked in a slew of scripts, only to realize that the file
> permissions were too open (I want them to be chmod 700, not chmod
> 755).  Somehow I thought that git was tracking those permission bits,
> but simply using "chmod 700 <fileset>; git add <fileset>" did not add
> the change of file modes, well, at least git status output doesn't
> show it. Is there a way to do this?

git doesn't track permissions quite that closely; all it remembers is whether the file should be executable or not.

-Jan
Previous: Lars NoschinskiNext: Brent Goodrick
Message 3 of 8 in “How can I force git to recognize a change change in file modes?”
  1. Brent GoodrickFeb 28, 2009
  2. Lars NoschinskiFeb 28, 2009
  3. Jan KrügerFeb 28, 2009
  4. Brent GoodrickFeb 28, 2009
  5. Jay SoffianFeb 28, 2009
  6. Brent GoodrickFeb 28, 2009
  7. Todd ZullingerFeb 28, 2009
  8. Brent GoodrickFeb 28, 2009

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.