* --simplify-merges breakage
@ 2013-04-08 19:00 Kevin Bracey
2013-04-08 19:54 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: Kevin Bracey @ 2013-04-08 19:00 UTC (permalink / raw)
To: git, Junio C Hamano
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: --simplify-merges breakage
2013-04-08 19:00 --simplify-merges breakage Kevin Bracey
@ 2013-04-08 19:54 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2013-04-08 19:54 UTC (permalink / raw)
To: Kevin Bracey; +Cc: git
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-04-08 19:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-08 19:00 --simplify-merges breakage Kevin Bracey
2013-04-08 19:54 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).