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

On Sat, May 14, 2016 at 6:30 PM, Junio C Hamano wrote: > Robert Dailey 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

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

Robert Dailey 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? -- To unsubscribe from this list: send the

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

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

Git log three-dot notation: include merge base

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,