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

Re: Should update-index --refresh force writing the index in case of racy timestamps?

From
Marc Strapetz <marc.strapetz@syntevo.com>
Date
Dec 17, 2021, 11:04 UTC
Message-ID
<505637a9-f6de-8f0d-b5cf-e765388f9301@syntevo.com>
In-Reply-To
<d3dd805c-7c1d-30a9-6574-a7bfcb7fc013@syntevo.com>
On 17/12/2021 11:44, Marc Strapetz wrote:
> Subsequent calls to "git update-index --refresh" or "git status" will invoke the "lfs" 
> filter over and over again, ...

Please forget about the note regarding "git status". cmd_status() will actually fix racy timestamps by calling repo_update_index_if_able(). So the problem is only about update-index.

-Marc
Previous: Marc StrapetzNext: brian m. carlson
Message 2 of 5 in “Should update-index --refresh force writing the index in case of racy timestamps?”
  1. Marc StrapetzDec 17, 2021
  2. Marc StrapetzDec 17, 2021
  3. brian m. carlsonDec 17, 2021
  4. Junio C HamanoDec 18, 2021
  5. Marc StrapetzDec 22, 2021

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.