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
Brent Goodrick <bgoodr@gmail.com>
Date
Feb 28, 2009, 17:34 UTC
Message-ID
<e38bce640902280934u3d9da650ke64865d7149b3c66@mail.gmail.com>
In-Reply-To
<76718490902280852y2f2657ck7459c138205bb874@mail.gmail.com>
Show 7 quoted lines
> The short answer is: because Git was designed to track content. The
> long answer is more complicated. Here's one of the more useful past
> discussions:
>
> http://thread.gmane.org/gmane.comp.version-control.git/91783
>
> I'm sure you can find others by searching the git list for "metadata".

I read that thread you showed above. Sounds like a big squirmy can-o-worms, and I see that thread died on the vine because of it. :)

All I want to do in my case is just chmod 700 a bunch of scripts after they are checked out or updated. I'll need to re-read the git-hooks man page more closely.

Thanks for your help! bg

Previous: Jay SoffianNext: Todd Zullinger
Message 6 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.