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

Difference between --date-order and reverse chronological order?

From
Dun Peal <dunpealer@gmail.com>
Date
Apr 27, 2011, 15:15 UTC
Message-ID
<12e0244a-313e-4d67-9b91-c0d443276cff@k7g2000yqj.googlegroups.com>
Hi.
The git-log manpage defines --date-order:

"This option is similar to --topo-order in the sense that no parent comes before all of its children, but otherwise things are still ordered in the commit timestamp order."

But by Git's definition, for a child commit to be created, its parent must already exist. So even in reverse chronological order, all parents should come after all their children, no?

Thanks, D.
Next: Junio C Hamano
Message 1 of 3 in “Difference between --date-order and reverse chronological order?”
  1. Dun PealApr 27, 2011
  2. Junio C HamanoApr 27, 2011
  3. Johannes SixtApr 27, 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.