Hi, the list of branches on https://perf.haskell.org/ghc 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 [email protected] • https://www.joachim-breitner.de/ XMPP: [email protected] • OpenPGP-Key: 0xF0FBF51F Debian Developer: [email protected]
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
