The Buildbot announcements that make it to the list signify critical issues: build machines going down. I will look into making the emails go to the machine owner.
Kindly, Dmitry > On May 26, 2015, at 8:28 PM, Carlos Santana <[email protected]> wrote: > > Agree dev@ being noisy with build bot announcements. > > On Thu, May 21, 2015 at 3:11 PM Shazron <[email protected]> wrote: > >> Yup, make sure your sender subscribes by sending an email to >> [email protected] first. >> Send an email to [email protected] for more info >> >> On Thu, May 21, 2015 at 12:03 PM, Jesse <[email protected]> wrote: >>> We do. [email protected] >>> There is duplication with github, so if it is too noisy you'll need to >>> setup filters. >>> >>> @purplecabbage >>> risingj.com >>> >>> On Thu, May 21, 2015 at 11:56 AM, Dmitry Blotsky <[email protected] >>> >>> wrote: >>> >>>> Hey folks, >>>> >>>> Do we have something like a [email protected]<mailto: >>>> [email protected]>? If so, do you think we should, so we don't >>>> keep getting commits and PRs to [email protected]<mailto: >>>> [email protected]>? Or is sending them to dev@ fine? >>>> >>>> Kindly, >>>> Dmitry >>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
