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

Re: [PATCH] log --graph: draw '>' and '<' with --left-right

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 22, 2008, 12:47 UTC
Message-ID
<alpine.DEB.1.00.0805221344360.30431@racer>
In-Reply-To
<alpine.DEB.1.00.0805221235430.30431@racer>
Hi,
On Thu, 22 May 2008, Johannes Schindelin wrote:
> 
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Sverre just notified me that the commit message is not brilliant. How about this:

-- snip -- When calling "git log --left-right <branch1>...<branch2>", a single "<" or ">" is shown in front of the commit line, to indicate which branch1 this commit comes from, branch1 or branch2.

However, it is easy to miss in the output of "git log --graph ...", since the graph still has "*" for regular commits and "M" for merge commits. So imitate gitk, and show the "<" and ">" characters in the graph, too, instead of "*" (or "M"). -- snap --

Thanks, Dscho

Previous: Johannes SchindelinNext: Sverre Rabbelier
Message 2 of 6 in “log --graph: draw '>' and '<' with --left-right”
  1. log --graph: draw '>' and '<' with --left-rightJohannes Schindelin, May 22, 2008
  2. Johannes SchindelinMay 22, 2008
  3. Sverre RabbelierMay 22, 2008
  4. Junio C HamanoMay 25, 2008
  5. Adam SimpkinsMay 25, 2008
  6. log and rev-list: don't print extra prefixes already shown in the graphAdam Simpkins, May 25, 2008

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.