Commit Notifications Flood

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Commit Notifications Flood

Ara Adkins
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

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Commit Notifications Flood

Ben Gamari-2
Ara Adkins <[hidden email]> 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

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (497 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Commit Notifications Flood

GHC - devs mailing list
In reply to this post by Ara Adkins

I’m getting them too

 

From: ghc-devs [mailto:[hidden email]] On Behalf Of Ara Adkins
Sent: 20 November 2017 21:07
To: GHC developers <[hidden email]>
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


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Commit Notifications Flood

Ara Adkins
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 <[hidden email]> wrote:

I’m getting them too

 

From: ghc-devs [mailto:[hidden email]] On Behalf Of Ara Adkins
Sent: 20 November 2017 21:07
To: GHC developers <[hidden email]>
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



_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Commit Notifications Flood

Ben Gamari-2
Ara Adkins <[hidden email]> 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


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (497 bytes) Download Attachment