Re: [all] dev@ traffic

2017-06-19 Thread Emmanuel Bourg
Le 19/06/2017 à 15:41, Stefan Bodewig a écrit : > those two should go to the same list even if its "issues"? Yes, sorry for the ambiguity. Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For addition

Re: [all] dev@ traffic

2017-06-19 Thread Simon Spero
On Jun 19, 2017 9:56 AM, "Stefan Bodewig" wrote: On 2017-06-19, Simon Spero wrote: with all parenteses properly nested, wow ;-) No need to apologize, really. (apply #'append '((not) (a problem)))

Re: [all] dev@ traffic

2017-06-19 Thread Stefan Bodewig
On 2017-06-19, Simon Spero wrote: > (this was prompted by me interrupting a quasi-appropriate JIRA > meta-discussion about JIRA workflow & permissions (on an issue I had opened > because I encountered it whilst working another issue, and had fixed but > not PRed, which Stefan then also fixed) to

Re: [all] dev@ traffic

2017-06-19 Thread Simon Spero
(this was prompted by me interrupting a quasi-appropriate JIRA meta-discussion about JIRA workflow & permissions (on an issue I had opened because I encountered it whilst working another issue, and had fixed but not PRed, which Stefan then also fixed) to further apologize to Stefan for not replyin

Re: [all] dev@ traffic

2017-06-19 Thread Stefan Bodewig
On 2017-06-19, Emmanuel Bourg wrote: > Le 19/06/2017 à 12:32, Stefan Bodewig a écrit : >> IMHO neither should go to dev@ and using notifications@ seems more >> logical to me. I'm going to change this for Compress and would likt to >> ask other components to check their settings as well so we can

Re: [all] dev@ traffic

2017-06-19 Thread sebb
On 19 June 2017 at 14:19, Emmanuel Bourg wrote: > Le 19/06/2017 à 12:32, Stefan Bodewig a écrit : > >> IMHO neither should go to dev@ and using notifications@ seems more >> logical to me. I'm going to change this for Compress and would likt to >> ask other components to check their settings as wel

Re: [all] dev@ traffic

2017-06-19 Thread Emmanuel Bourg
Le 19/06/2017 à 12:32, Stefan Bodewig a écrit : > IMHO neither should go to dev@ and using notifications@ seems more > logical to me. I'm going to change this for Compress and would likt to > ask other components to check their settings as well so we can raise the > signal ratio for dev@ again. +

[all] dev@ traffic

2017-06-19 Thread Stefan Bodewig
Hi all apart from dev@ and user@ we've got three lists that have been created for specific notifications that people may be interested in or not: issues, commits and notifications. My MUA is configured to merge those three with dev so I didn't really notice we are getting more messages (and for mo