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

Options to have git log presents commits of a non linear history in a meaningful order

From
Uu34@net9.cf <u34@net9.cf>
Date
May 13, 2024, 20:58 UTC
Message-ID
<E1s6cl5-0003nc-3D@mx1.net9.cf>

Am I right by default, git log present commits of a non linear history in a meaningles order? Am I right git log has options, such as --graph, to get the order of commits presented in a more meaningful way?

As of git 2.45.0, gittutorial states 
    
   The git log command has a weakness: it must present commits in
   a list. When the history has lines of development that
   diverged and then merged back together, the order in which git
   log presents those commits is meaningless.
Is it accurate?

-- u34

Next: Junio C Hamano
Message 1 of 2 in “Options to have git log presents commits of a non linear history in a meaningful order”
  1. u34@net9.cfMay 13, 2024
  2. Junio C HamanoMay 13, 2024

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.