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

git checkout behaviour when only ctime of file changes

From
CVCristian Morales Vega <christian.morales.vega@gmail.com>
Date
Apr 19, 2021, 09:11 UTC
Message-ID
<CAOWQn3Qesh0+CkaD95q78Rq_vN5tjWKDe7HTk0Ynk-NY8XUKzg@mail.gmail.com>

I thought you may want to take a look at https://issues.jenkins.io/browse/JENKINS-65395.

Basically after something updates the ctime of a file, a "git checkout" can behave differently depending on whether a "git update-index --refresh" has been run before or not. _Maybe_ it could make sense for "git checkout" to always behave as if "git update-index --refresh" had been run before? No idea really.

I have seen this with git version 2.30.2.
Next: Bagas Sanjaya
Message 1 of 6 in “git checkout behaviour when only ctime of file changes”
  1. Cristian Morales VegaApr 19, 2021
  2. Bagas SanjayaApr 19, 2021
  3. Cristian Morales VegaApr 19, 2021
  4. Junio C HamanoApr 19, 2021
  5. brian m. carlsonApr 20, 2021
  6. Cristian Morales VegaApr 20, 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.