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

A better git log --graph?

From
YDYuri D'Elia <wavexx@thregr.org>
Date
Jan 7, 2015, 14:23 UTC
Message-ID
<m8jfg5$dsp$1@ger.gmane.org>
Hi everyone,

git log --graph is hard for me to parse mentally when developing a project which has a lot of branches.

All the tools I've been using seem to just parse log --graph's output, and thus are no better at showing history.

I would love to have a graph mode where each branch is assigned a column, and stays there. If my log section shows the history of 3 branches, column 1 should always refer to master, 2 to the hypothetical "development" branch and 3 to "feature".

Of course the mode will waste more horizontal space, but it would be immediately more apparent which branch is merging into which.

I saw this idea proposed a couple of times in the mailing list, but I saw no "action" behind the proposal. Since I don't have time to work on it, has anyone already started some work that he would like to share as a starting point? Even just to have a felling if it's worth the effort.

Does anybody know of another tool to graph the history using something that is not based on git log --graph?

I've seen a couple of graphviz-based ones, but both failed to work out of the box for me.

Thanks a lot for any pointer.
Next: Johan Herland
Message 1 of 6 in “A better git log --graph?”
  1. Yuri D'EliaJan 7, 2015
  2. Johan HerlandJan 7, 2015
  3. Yuri D'EliaJan 7, 2015
  4. Junio C HamanoJan 7, 2015
  5. Yuri D'EliaJan 8, 2015
  6. John SzakmeisterJan 8, 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.