simple pictures about GHC development flow

Takenobu Tani takenobu.hs at gmail.com
Sun Oct 30 02:25:56 UTC 2016


Hi Ben, Joachim,

2016-10-30 2:07 GMT+09:00 Ben Gamari <ben at smart-cactus.org>:
> Nope, that's exactly right. Unfortunately, even "trivial" fixes have a
> tendency to break the tree (which has been happening too often recently)
> so I'm trying to push contributors to use CI whenever possible.

Thank you for explaining me.
I understand the reason that you are talking about travis.


2016-10-30 2:59 GMT+09:00 Joachim Breitner <mail at joachim-breitner.de>:
> I see. The term “flow” suggested something deeper or more structured
> (which might be good, but is not the case). Maybe relabel it “direct
> commit”.

Thank you.
I'll update the "committer flow" to "direct commit" on page 7.
It is more clear about the current situation.

Regards,
Takenobu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20161030/88f2cd3c/attachment.html>


More information about the ghc-devs mailing list