RE:’s list of branches got more useful

Simon Peyton Jones simonpj at
Mon Apr 25 09:32:17 UTC 2016



But your email will soon disappear into the mists of time, and the page itself does not convey the same information.  

Is there a wiki page, kept up to date, that explains exactly how to read the performance results?


|  -----Original Message-----
|  From: ghc-devs [mailto:ghc-devs-bounces at] On Behalf Of
|  Joachim Breitner
|  Sent: 23 April 2016 20:41
|  To: ghc-devs at
|  Subject:’s list of branches got more useful
|  Hi,
|  the list of branches
|  on
|  c0ca8588956494efa3308d36baf36f5%7c72f988bf86f141af91ab2d7cd011db47%7c1&
|  sdata=Rk2Y38BjXeE9Et8yxiuOdpiJ3PSMn9RdIxonRksxTc4%3d got more useful.
|  It now shows the difference from the branch head to the merge base¹,
|  which should roughly exhibit the performance change that would be
|  caused by merging the branch into master.
|  If the branch head or the merge base have not been measured (e.g.
|  because the build failed), the display might be a bit confusing. Same
|  with branches that often merge or cherry-pick from master. But in the
|  common case of a linear, possibly rebased, feature branch, it should
|  work fine.
|  Greetings,
|  Joachim
|  ¹ Which, I think, is the youngest commit also reachable from master. Or
|  something like that. Consult "man git merge-base" if you want a little
|  mind teaser.
|  --
|  Joachim “nomeata” Breitner
|    mail at|
|  achim-
|  588956494efa3308d36baf36f5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata
|  =ya%2bnaZWlbasw8BSIICImvWjh1x%2fb6%2bTsHJuKRGzu2Rg%3d
|    XMPP: nomeata at • OpenPGP-Key: 0xF0FBF51F
|    Debian Developer: nomeata at

More information about the ghc-devs mailing list