Re: Commit Notifications Flood

I've put a redirect rule on them for now, but given that this is the second time that it's happened (as far as I know), is it possible to modify the way in which the commit hook sends notifications for new branches with a significant history? I don't really know much about the exact message generation process, but perhaps it is possible to provide a digest when pushing a new branch. Something that lists the branch name and the number of commits, for example. Best, _ara On Mon, Nov 20, 2017 at 11:01 PM, Simon Peyton Jones wrote:

I’m getting them too ☹

*From:* ghc-devs [mailto:ghc-devs-bounces@haskell.org] *On Behalf Of *Ara Adkins *Sent:* 20 November 2017 21:07 *To:* GHC developers *Subject:* Commit Notifications Flood

Is anyone else getting an absolute flood of commit emails related to haddock? I remember this happening a little while back with the hadrian merge into the GHC tree.

Best,

_ara