Re: Commit mailinglists

On 2011-08-17, Christian Grobmeier wrote:

> On Wed, Aug 17, 2011 at 9:26 AM, Stefan Bodewig <[email protected]> wrote:
>> I don't know why commit mails go to the general list, but this one
>> caught my eye:

> It should go to [email protected] to my knowledge
> But looking at the headers they all go to [email protected]

This is the current configuration

,----
| # Logging
| [/logging]
| for_paths = logging/
| to_addr = [email protected]
| 
| [/logging/sandbox]
| for_paths = logging/sandbox/
| to_addr = [email protected]
| 
| [/logging/log4j]
| for_paths = logging/log4j/
| to_addr = [email protected]
| 
| [/logging/log4cxx]
| for_paths = logging/log4cxx/
| to_addr = [email protected]
| 
| [/logging/log4net]
| for_paths = logging/log4net/
| to_addr = [email protected]
| 
| [/logging/log4php]
| for_paths = logging/log4php/
| to_addr = [email protected]
`----

So this looks OK for most sub-projects.  chainsaw lives directly under
logging so the fallback is the only one that matches.  Should it go to a
different list instead?

Shall I expand INFRA-3858 (make the mbox archive of log4net-cvs public)
to include the other *-cvs lists in addition as well?

Stefan