RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently. ðŸ˜
RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently. ðŸ˜
Yeah, returning stuff from git history should only be a fallback for files without maintainers. I get my fair share of these Cc's and I'm always like WTF why am I included.
IMO it should also only include the most specific maintainers by default. If you have the maintainer for file foo/bar/baz, don't include the maintainer for foo/bar or foo.
@jani @kees the whole inheritance thing is kinda broken actually see [0] for an example of this being broken :)
Stuff lower in hierarchy that potentially impacts stuff higher up is not cc'd to those subject to it, stuff higher up does include lower-down etc.
I guess we need to distinguish between 'anything in this glob that's not already handled elsewhere' vs. 'I want to be cc'd on everything here'.
cc: @vbabka who loves editing get_maintainer.pl :P
https://lore.kernel.org/all/2026030820[email protected]/T/#u