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

Consistency question

From
David Kastrup <dak@gnu.org>
Date
Jan 15, 2014, 10:37 UTC
Message-ID
<8761pl8raj.fsf@fencepost.gnu.org>
Hi,

I am in the process of rewriting the core logic of git blame (the current speed of which is quite an impediment to some workflows). I currently have one question I don't see an answer to right away, and that question arises in doing a reasonably robust traversal of commits without determining topology first:

The question is what guarantees I have with regard to the commit date of a commit in relation to that of its parent commits:

a) none b) commitdate(child) >= commitdate(parent) c) commitdate(child) > commitdate(parent)

Obviously, I can rely on c) being true "almost always": it's definitely good for a heuristic used for improving performance (meaning as an ordering criterion for a commit priority queue). The problem is how much I should cater for graceful behavior for the cases where it's not.

Does git do any actual checks before pushing?
-- 
David Kastrup
Next: Jeff King
Message 1 of 8 in “Consistency question”
  1. David KastrupJan 15, 2014
  2. Jeff KingJan 15, 2014
  3. David KastrupJan 15, 2014
  4. Andreas KreyJan 15, 2014
  5. David KastrupJan 15, 2014
  6. Andreas KreyJan 15, 2014
  7. David KastrupJan 15, 2014
  8. Mike HommeyJan 18, 2014

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.