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
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 28, 2009, 16:52 UTC
Message-ID
<76718490902280852y2f2657ck7459c138205bb874@mail.gmail.com>
In-Reply-To
<e38bce640902280824x3ae41d95qab1f1a450235e096@mail.gmail.com>
On Sat, Feb 28, 2009 at 11:24 AM, Brent Goodrick <bgoodr@gmail.com> wrote:
> Thanks Jan.  Was this choice made due to the conditional coding
> required to track the permission bits content between *NIX and
> non-*NIX platform(s)?

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".
j.
Previous: Brent GoodrickNext: Brent Goodrick
Message 5 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.