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, 22:43 UTC
Message-ID
<e38bce640902281443x69bd64ebuf4aa784be220b6bb@mail.gmail.com>
In-Reply-To
<20090228183427.GN4505@inocybe.teonanacatl.org>
On Sat, Feb 28, 2009 at 10:34 AM, Todd Zullinger <tmz@pobox.com> wrote:
> You may want to check contrib/hooks/setgitperms.perl as well, if you
> haven't seen it already.

Yes I did see that. I'll be varying that approach a bit since I won't need to preserve perm bits before and after the git operation, but just force them to be a specific value all the time after checkout and update.

bg
Previous: Todd Zullinger
Message 8 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.