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

Re: Git log three-dot notation: include merge base

From
Junio C Hamano <gitster@pobox.com>
Date
May 14, 2016, 23:30 UTC
Message-ID
<xmqqbn486wv3.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0+uTsxg@mail.gmail.com>
Robert Dailey <rcdailey.lists@gmail.com> writes:
> This is because the merge base commit isn't shown. I understand this
> is "by-design", but is there a way to include it? It's necessary to
> have it, for this graph to make sense.
--boundary, perhaps?
Previous: Jeff KingNext: Robert Dailey
Message 3 of 4 in “Git log three-dot notation: include merge base”
  1. Robert DaileyMay 14, 2016
  2. Jeff KingMay 14, 2016
  3. Junio C HamanoMay 14, 2016
  4. Robert DaileyMay 14, 2016

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.