Another possible alternative is to make the standard be that people create a pull request on github but are still required to send an email to this group announcing the pull request, briefly explaining it's purpose, and providing a link to it. That way this email list still at least get a notification but would be spared from a potential flood of automated messages. However, I can foresee confusion on if resulting discussions should occur via email or via github.
For example: Subject: Adding support for AwesomeProtocol Body: I have created a pull request that adds support for the AwesomeProtocol, which is documented at http://www.example.com/AwesomeProtocol. Blah blah blah. Please review the pull request at https://github.com/bagder/curl/pull/<IDHere>. Patrick Patrick On Wed, Feb 25, 2015 at 1:55 PM, moparisthebest <[email protected]> wrote: > On 02/25/2015 01:29 PM, Rich Gray wrote: > > I suspect filtering it out of the digests would not be easy. > > I meant the list software at [email protected] could filter it > before sending/including in digests so that only new pull request > discussions would get sent out, to keep it the same amount of traffic as > if they didn't put in a pull request and just emailed the list like they > do now. > > Either way would be fine though. > > Thanks, > moparisthebest > ------------------------------------------------------------------- > List admin: http://cool.haxx.se/list/listinfo/curl-library > Etiquette: http://curl.haxx.se/mail/etiquette.html >
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
