# --simplify-merges breakage

2 messages from 2013-04-08 to 2013-04-08. Participants: Kevin Bracey, Junio C Hamano.
Thread: https://gitlist.dev/t/33439

## Kevin Bracey, 2013-04-08 19:00

Subject: --simplify-merges breakage
Message-ID: <516313D3.2050309@bracey.fi>
URL: https://gitlist.dev/e/516313D3.2050309%40bracey.fi

```
Commit 4b7f53d ("simplify-merges: drop merge from irrelevant side 
branch") appears to have broken simplify-merges.

[Credit to "git bisect run" - and now I see the "report problems 
immediately" message on the recent merge of that change.]

I was trying to get my head around history simplification, by creating a 
repo with the example shown in the manual.The result of "gitk 
--simplify-merges foo" was far from pretty.

With the example in the manual, you should get this:

           .-A---M---N---O
          /     /       /
         I     B       D
          \   /       /
           `---------'

After 4b7f53 you instead get:

           .-A---M   N---O
         /     /   /   /
         I     B   /   D
          \   /   /   /
           `---------'

Kevin

```

## Junio C Hamano, 2013-04-08 19:54

Subject: Re: --simplify-merges breakage
Message-ID: <7vfvz0x0gs.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vfvz0x0gs.fsf%40alter.siamese.dyndns.org
In-Reply-To: <516313D3.2050309@bracey.fi>

```
Kevin Bracey <kevin@bracey.fi> writes:

> Commit 4b7f53d ("simplify-merges: drop merge from irrelevant side
> branch") appears to have broken simplify-merges.
>
> ... now I see the "report problems
> immediately" message on the recent merge of that change.

I hope more people now see why we would like to see more people try
'next' regularly.

Will revert it for now, but that would mean side histories like gitk's
will keep showing up in the simplified view.

```