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

Re: Git on Windows maps creation time onto changed time

From
KGKeith Goldfarb <keith@blackthorn-media.com>
Date
Feb 2, 2018, 18:45 UTC
Message-ID
<040E3C3E-BC8E-4658-A882-5149D10AD408@blackthorn-media.com>
In-Reply-To
<c1e419ae-feae-5a31-ead6-20b25fa92f85@kdbg.org>
> The purpose of these values is to allow to notice a change on the file system without going through the actual file data. Duplicating st_mtime would be pointless.
Well, I agree with the first statement. I disagree with the 2nd. It’s not pointless to fix a problem, and in theory the creation date of a file can never change.
> Don't do that then. Use core.trustctime.
I am. Unfortunately, my problem isn’t solved by that alone. Perhaps this deserves its own thread, but on Windows the st_ino field is set to zero. This can also trigger a false positive, causing the whole cache to be rebuilt unnecessarily.
K.
Previous: Johannes SixtNext: Johannes Schindelin
Message 4 of 7 in “Git on Windows maps creation time onto changed time”
  1. Keith GoldfarbFeb 1, 2018
  2. Ævar Arnfjörð BjarmasonFeb 1, 2018
  3. Johannes SixtFeb 2, 2018
  4. Keith GoldfarbFeb 2, 2018
  5. Johannes SchindelinFeb 2, 2018
  6. Keith GoldfarbFeb 2, 2018
  7. Johannes SchindelinFeb 2, 2018

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.