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

Possible timestamp problems with diff-files?

From
Marc Strapetz <marc.strapetz@syntevo.com>
Date
Sep 20, 2011, 10:30 UTC
Message-ID
<4E786B5D.40601@syntevo.com>
For our Git client, we are invoking
git diff-files--quiet --ignore-submodules

immediately after a commit of *all* changes. Hence, the expected exit code would be 0 (because there are no changes). A user has now reported that for commits with many changes, exit code is sometimes 1. For the last incident, the commit was started at 15:24:11,820 and finished at 15:24:12,329, diff-files was invoked at 15:24:12,455 and failed with exit code 1 at 15:24:21,394. A subsequent diff-files succeeded, so I'm wondering now, if that could be a timestamp problem (maybe related to the Index)?

Note that there are a couple of threads running in the client itself, so I guess actual running time of diff-files was much shorter than 9 seconds and chances are that some parts of diff-files were run in the same second 15:24:12.

System configuration is: Linux splitter 2.6.38-11-server #48-Ubuntu SMP Fri Jul 29 19:20:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

git version 1.7.4.1

-- Best regards, Marc Strapetz ============= syntevo GmbH http://www.syntevo.com http://blog.syntevo.com

Next: Jeff King
Message 1 of 5 in “Possible timestamp problems with diff-files?”
  1. Marc StrapetzSep 20, 2011
  2. Jeff KingSep 20, 2011
  3. Marc StrapetzSep 21, 2011
  4. Junio C HamanoSep 21, 2011
  5. Robin RosenbergSep 24, 2011

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.