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

problem with modification time of packfiles

From
AAAndreas Amann <a.amann@ucc.ie>
Date
Oct 18, 2015, 21:37 UTC
Message-ID
<87io63503w.fsf@msstf091.ucc.ie>

git (2.6.1) sometimes updates the modification time of a packfile, even if it has not changed at all.

On my system this triggers quite expensive an d unnecessary backup operations, which I would prefer to avoid. Is there a simple way to keep the mtime of packfiles fixed, once they are created?

Apparently the undesired mtime update is done in sha1_file.c:freshen_file() which is called (indirectly) by write_sha1_file(). However I did not understand, why this is done.

Any clarification and pointers, how mtime can be kept constant would be appreciated.

Thanks, Andreas

Next: brian m. carlson
Message 1 of 5 in “problem with modification time of packfiles”
  1. Andreas AmannOct 18, 2015
  2. brian m. carlsonOct 19, 2015
  3. Andreas AmannOct 19, 2015
  4. brian m. carlsonOct 19, 2015
  5. Jeff KingOct 19, 2015

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.