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

Default ordering of git log output

From
Kirill Likhodedov <kirill.likhodedov@gmail.com>
Date
Sep 3, 2015, 13:50 UTC
Message-ID
<494BA1BD-150F-45A2-BF5D-9A933D9C1344@gmail.com>
Is it intended behavior that the default git log output (without ordering parameters) can show parents before children? 
The man says:
    Commit Ordering
       By default, the commits are shown in reverse chronological order.
so it tells nothing about parent-to-child relationship.
I‘ve just faced an example in an open source repository, where I reproduced this behavior: a parent is shown before its child. (so if this behavior is not intended I can give the project URL for debugging)
So could you please clarify:
1. Is it true that the rule "no parents before all of its children are shown” is not guaranteed for default ordering?
2. What does "reverse chronological order” mean? How commits are actually sorted in git log? 
// I was always under impression that git log lists commit in the order in which they are “recorded" to the repository (e.g. pulled), since this seems to be both the fastest way, and also pretty acceptable from the ordering point of view.  

Thanks a lot! -- Kirill.

Next: Junio C Hamano
Message 1 of 2 in “Default ordering of git log output”
  1. Kirill LikhodedovSep 3, 2015
  2. Junio C HamanoSep 3, 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.