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

Re: Forcing re-reading files with unchanged stats

From
Jeff King <peff@peff.net>
Date
Jan 13, 2011, 03:32 UTC
Message-ID
<20110113033217.GA32661@sigill.intra.peff.net>
In-Reply-To
<4D2E6D99.9060907@dbservice.com>
On Thu, Jan 13, 2011 at 04:12:25AM +0100, Tomas Carnecky wrote:
Show 11 quoted lines
>  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.

That won't work, as it respects the stat information. So does --really-refresh. AFAIK, there isn't a way to tell update-index to ignore start information, short of blowing away the index entirely, and doing a read-tree to repopulate it.

I'm curious what this use case is, and whether it would be acceptable to update something like ctime on the files to make them stat-dirty to git.

-Peff
Previous: Tomas CarneckyNext: Junio C Hamano
Message 3 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.