[Haskell-cafe] A suggestion: On why code merges should influence Haskell design
Sven Panne
svenpanne at gmail.com
Wed Oct 14 13:03:09 UTC 2015
2015-10-14 13:44 GMT+02:00 Erik Hesselink <hesselink at gmail.com>:
> I'm not sure why you're saying this is impossible with merges; I've
> done it several times. Git will find the right branch where things
> went wrong, and then finds the commit on that branch without problems.
Well, it might be the case that 'git bisect' alone works, but if you've got
lots of tooling sitting on top of your version control (e.g. bots measuring
and visualing performance, detecting regressions, etc.), you have a much
easier time with a linear history than a DAG-shaped one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20151014/453158f3/attachment.html>
More information about the Haskell-Cafe
mailing list