Commit Notifications Flood

Ara Adkins

20 Nov 2017 20 Nov '17

4:06 p.m.

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

Attachments:

attachment.html (text/html — 233 bytes)

Show replies by date

Ben Gamari

20 Nov 20 Nov

5:58 p.m.

Ara Adkins writes:

...

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.

Indeed it seems that the commit hook is running amuck [1] Herbert, do you know what we can do about this? Cheers, - Ben [1] https://mail.haskell.org/pipermail/ghc-commits/2017-November/thread.html

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

Ara Adkins

6:18 p.m.

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

Ben Gamari

7:36 p.m.

Ara Adkins writes:

...

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.

Indeed we really should set an upper bound on the number of messages that it will send. I agree that this is quite ridiculous. Cheers, - Ben

2738

Age (days ago)

2739

Last active (days ago)

List overview

Download

4 comments

3 participants

participants (3)

Ara Adkins
Ben Gamari
Simon Peyton Jones