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
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 17, 2021, 21:14 UTC
Message-ID
<Ybz9ruQ/uOfFbn3W@camp.crustytoothpaste.net>
In-Reply-To
<d3dd805c-7c1d-30a9-6574-a7bfcb7fc013@syntevo.com>
On 2021-12-17 at 10:44:32, Marc Strapetz wrote:
Show 9 quoted lines
> For one of my Git-LFS test repositories, switching between branches quite
> often results in lots of racy index timestamps. Subsequent calls to "git
> update-index --refresh" or "git status" will invoke the "lfs" filter over
> and over again, just to figure out that all entries are still up-to-date.
> Hence, the index will never be rewritten and racy timestamps will remain.
> 
> To break out of this state, it seems favorable to write the index if any
> racy timestamp is detected. We will be able to provide a patch if this
> change sounds reasonable.

Sure, this sounds reasonable, especially if, as you mentioned, git status already does this. We might as well make the plumbing commands as functional as the porcelain commands.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
Previous: Marc StrapetzNext: Junio C Hamano
Message 3 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.