# Git log three-dot notation: include merge base

4 messages from 2016-05-14 to 2016-05-14. Participants: Robert Dailey, Jeff King, Junio C Hamano.
Thread: https://gitlist.dev/t/42324

## Robert Dailey, 2016-05-14 23:09

Subject: Git log three-dot notation: include merge base
Message-ID: <CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0+uTsxg@mail.gmail.com>
URL: https://gitlist.dev/e/CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0%2BuTsxg%40mail.gmail.com

```
If you consider a simple case where I run the following command:

$ git log --oneline --graph --decorate A...B

Where A and B are both branches with a single merge base and a series
of commits on each branch. Very simple example with no loops or crazy
ancestry. Below is an example repo I set up, where I show the whole
repository log graph:

$ git log --oneline --decorate --graph --all
* eb28ae4 (HEAD -> B) Commit 6
* 7173fa1 Commit 5
* b5fe27b Commit 4
| * 37a8ca8 (A) Commit 3
| * 72745a7 Commit 2
|/
* ffc8040 Commit 1

Using A...B notation, I get this:

$ git log --oneline --decorate --graph A...B
* eb28ae4 (HEAD -> B) Commit 6
* 7173fa1 Commit 5
* b5fe27b Commit 4
* 37a8ca8 (A) Commit 3
* 72745a7 Commit 2

The graph no longer makes any sense, and isn't helpful to me at all.
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.

```

## Jeff King, 2016-05-14 23:22

Subject: Re: Git log three-dot notation: include merge base
Message-ID: <20160514232211.GA26038@sigill.intra.peff.net>
URL: https://gitlist.dev/e/20160514232211.GA26038%40sigill.intra.peff.net
In-Reply-To: <CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0+uTsxg@mail.gmail.com>

```
On Sat, May 14, 2016 at 06:09:21PM -0500, Robert Dailey wrote:

> Using A...B notation, I get this:
> 
> $ git log --oneline --decorate --graph A...B
> * eb28ae4 (HEAD -> B) Commit 6
> * 7173fa1 Commit 5
> * b5fe27b Commit 4
> * 37a8ca8 (A) Commit 3
> * 72745a7 Commit 2
> 
> The graph no longer makes any sense, and isn't helpful to me at all.
> 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.

Try "--boundary".

-Peff

```

## Junio C Hamano, 2016-05-14 23:30

Subject: Re: Git log three-dot notation: include merge base
Message-ID: <xmqqbn486wv3.fsf@gitster.mtv.corp.google.com>
URL: https://gitlist.dev/e/xmqqbn486wv3.fsf%40gitster.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?

```

## Robert Dailey, 2016-05-14 23:32

Subject: Re: Git log three-dot notation: include merge base
Message-ID: <CAHd499D2ci-8WKh=sCGdoy_Ry7aCw+TxD_Rp7QWiUpg9Qu=nmA@mail.gmail.com>
URL: https://gitlist.dev/e/CAHd499D2ci-8WKh%3DsCGdoy_Ry7aCw%2BTxD_Rp7QWiUpg9Qu%3DnmA%40mail.gmail.com
In-Reply-To: <xmqqbn486wv3.fsf@gitster.mtv.corp.google.com>

```
On Sat, May 14, 2016 at 6:30 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 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?

Big thanks to both you and Jeff. I figured there was some option for
this, but I always have trouble finding what I need in the
documentation sea of git log :-)

This worked perfectly. Much appreciated!!!

```