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

Re: Forcing re-reading files with unchanged stats

From
Tomas Carnecky <tom@dbservice.com>
Date
Jan 13, 2011, 03:12 UTC
Message-ID
<4D2E6D99.9060907@dbservice.com>
In-Reply-To
<loom.20110112T150313-103@post.gmane.org>
  On 1/12/11 3:07 PM, Maaartin wrote:
> There are files in my working tree which changes, but their size and mtime
> remains the same (I know it's strange, but it's useful). Can I make git to re-
When can this be useful?
> read them all, so it recognizes the change? Ideally, using a configuration
> variable. The repo is fairly small, so speed is no issue here.

Try git update-index --refresh. I'm not aware of any config option, but you might want to look through man git-config.

tom
Previous: MaaartinNext: Jeff King
Message 2 of 5 in “Forcing re-reading files with unchanged stats”
  1. MaaartinJan 12, 2011
  2. Tomas CarneckyJan 13, 2011
  3. Jeff KingJan 13, 2011
  4. Junio C HamanoJan 13, 2011
  5. Maaartin-1Jan 14, 2011

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.