Re: Commit Notifications Flood

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

Re: Commit Notifications Flood

them too ☹ > > > > *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Ara > Adkins > *Sent:* 20 November 2017 21:07 > *To:* GHC developers <ghc-devs@haskell.org> > *Subject:* Commit Notifications Flood > > > > Is anyone else getting an absolute floo

RE: Commit Notifications Flood

I’m getting them too ☹ From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Ara Adkins Sent: 20 November 2017 21:07 To: GHC developers <ghc-devs@haskell.org> Subject: Commit Notifications Flood Is anyone else getting an absolute flood of commit emails related to haddock? I re

Re: Commit Notifications Flood

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

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 ghc-devs@haskell.org