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.

[kees@hachyderm.io]

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.

[ted@social.gould.cx]

@kees teach you to try and make things better

[corbet@social.kernel.org]

@kees Gee, sounds like being the docs maintainer

[ermo@fosstodon.org]

@kees Oof.

[jani@floss.social]

@kees I'm eagerly waiting for your upcoming patches to get_maintainer.pl next.

[jani@floss.social]

@ljs @kees

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@floss.social]

@ljs @kees

Oh, and the primary reason I only whine and moan here instead of sending patches is that the damn thing is written in Perl. Plus I don't want to get Cc'd for patches touching get_maintainer.pl in the future. No wait.

[ptesarik@infosec.exchange]

@ljs @jani @kees @vbabka Ugh, why is this still written in Perl?
Why didn't someone rewrite it in—I don't know—Brainfuck?