{"thread":{"id":"42324","subject":"Git log three-dot notation: include merge base","startedAt":"2016-05-14T23:09:21Z","lastAt":"2016-05-14T23:32:39Z","messageCount":4,"participants":["Robert Dailey","Jeff King","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"286551","messageId":"CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0+uTsxg@mail.gmail.com","threadId":"42324","inReplyTo":null,"subject":"Git log three-dot notation: include merge base","fromName":"Robert Dailey","fromEmail":"rcdailey.lists@gmail.com","sentAt":"2016-05-14T23:09:21Z","receivedAt":"2016-05-14T23:09:21Z","isPatch":false,"sender":{"key":"rcdailey.lists@gmail.com","avatar":null},"body":"If you consider a simple case where I run the following command:\n\n$ git log --oneline --graph --decorate A...B\n\nWhere A and B are both branches with a single merge base and a series\nof commits on each branch. Very simple example with no loops or crazy\nancestry. Below is an example repo I set up, where I show the whole\nrepository log graph:\n\n$ git log --oneline --decorate --graph --all\n* eb28ae4 (HEAD -> B) Commit 6\n* 7173fa1 Commit 5\n* b5fe27b Commit 4\n| * 37a8ca8 (A) Commit 3\n| * 72745a7 Commit 2\n|/\n* ffc8040 Commit 1\n\nUsing A...B notation, I get this:\n\n$ git log --oneline --decorate --graph A...B\n* eb28ae4 (HEAD -> B) Commit 6\n* 7173fa1 Commit 5\n* b5fe27b Commit 4\n* 37a8ca8 (A) Commit 3\n* 72745a7 Commit 2\n\nThe graph no longer makes any sense, and isn't helpful to me at all.\nThis is because the merge base commit isn't shown. I understand this\nis \"by-design\", but is there a way to include it? It's necessary to\nhave it, for this graph to make sense.\n"},{"id":"286552","messageId":"20160514232211.GA26038@sigill.intra.peff.net","threadId":"42324","inReplyTo":"CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0+uTsxg@mail.gmail.com","subject":"Re: Git log three-dot notation: include merge base","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-05-14T23:22:11Z","receivedAt":"2016-05-14T23:22:11Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, May 14, 2016 at 06:09:21PM -0500, Robert Dailey wrote:\n\n> Using A...B notation, I get this:\n> \n> $ git log --oneline --decorate --graph A...B\n> * eb28ae4 (HEAD -> B) Commit 6\n> * 7173fa1 Commit 5\n> * b5fe27b Commit 4\n> * 37a8ca8 (A) Commit 3\n> * 72745a7 Commit 2\n> \n> The graph no longer makes any sense, and isn't helpful to me at all.\n> This is because the merge base commit isn't shown. I understand this\n> is \"by-design\", but is there a way to include it? It's necessary to\n> have it, for this graph to make sense.\n\nTry \"--boundary\".\n\n-Peff\n"},{"id":"286553","messageId":"xmqqbn486wv3.fsf@gitster.mtv.corp.google.com","threadId":"42324","inReplyTo":"CAHd499A_AN0U7gj8Yp0pBGGZ6deNrDJ4F4npAKy6a2U0+uTsxg@mail.gmail.com","subject":"Re: Git log three-dot notation: include merge base","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-05-14T23:30:40Z","receivedAt":"2016-05-14T23:30:40Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Robert Dailey <rcdailey.lists@gmail.com> writes:\n\n> This is because the merge base commit isn't shown. I understand this\n> is \"by-design\", but is there a way to include it? It's necessary to\n> have it, for this graph to make sense.\n\n--boundary, perhaps?\n"},{"id":"286554","messageId":"CAHd499D2ci-8WKh=sCGdoy_Ry7aCw+TxD_Rp7QWiUpg9Qu=nmA@mail.gmail.com","threadId":"42324","inReplyTo":"xmqqbn486wv3.fsf@gitster.mtv.corp.google.com","subject":"Re: Git log three-dot notation: include merge base","fromName":"Robert Dailey","fromEmail":"rcdailey.lists@gmail.com","sentAt":"2016-05-14T23:32:39Z","receivedAt":"2016-05-14T23:32:39Z","isPatch":false,"sender":{"key":"rcdailey.lists@gmail.com","avatar":null},"body":"On Sat, May 14, 2016 at 6:30 PM, Junio C Hamano <gitster@pobox.com> wrote:\n> Robert Dailey <rcdailey.lists@gmail.com> writes:\n>\n>> This is because the merge base commit isn't shown. I understand this\n>> is \"by-design\", but is there a way to include it? It's necessary to\n>> have it, for this graph to make sense.\n>\n> --boundary, perhaps?\n\nBig thanks to both you and Jeff. I figured there was some option for\nthis, but I always have trouble finding what I need in the\ndocumentation sea of git log :-)\n\nThis worked perfectly. Much appreciated!!!\n"}]}