Re: [RFC v2] MAINTAINERS: split kselftest entry into 'framework' and 'all'

[Jakub Kicinski <kuba@kernel.org>]

On Fri, 22 Nov 2024 07:56:25 -0700 Shuah wrote:
> > To me the dissonance between your admission that people don't CC the
> > current list (IOW status quo isn't great) and the resistance to change
> > is fairly apparent. But it is obviously your call.  
> My thinking is that people don't seem to CC the one mailing list
> we have and adding one more would add to the problem.
> 
> Are there other ways to solve the problem by using prefix like
> we do now for subsystem tests: selftests:framework?

I think the ideal solution would be to let people subscribe to code
paths rather the deal with mailing lists in the first place :(
That way we can fix this on the "mailing list backend" rather than
expecting people who submit code to do the right thing.

Konstantin did some work on auto-CC based on get_maintainer output,
whether vger would just fill in the missing CCs, but AFAIR he got stuck
on the need to modify headers which would break DKIM.

I should mention that lore/lei does support filtering / subscribing 
to paths etc, but from experience bringing folks into upstream
reviews - running lore/lei doesn't work for everyone. I also don't 
use it because it doesn't support the mbox format of my MUA :(

At the current state of affairs, since we can't fix the "receiver" side
easily, we have to shift the responsibility on the "sender" side.
Hope people run get_maintainer, and have well defined lists..