Re: Validating MAINTAINERS entries?

[Geert Uytterhoeven <geert@linux-m68k.org>]

On Wed, Aug 10, 2022 at 2:50 PM Mark Brown <broonie@kernel.org> wrote:
> On Wed, Aug 10, 2022 at 03:04:50PM +0300, Dan Carpenter wrote:
> > On Wed, Aug 10, 2022 at 12:50:50PM +0100, Lee Jones wrote:
> > > I am presently plagued with reviews for lots of files that I've
> > > touched over the years.  Even if the changes were trivial.
>
> > > Or is this just an education point?
>
> > Education is not the answer.
>
> > We've got thousands of devs and no one can keep track of everyone and
> > their motives.
>
> I think the issue there is more that if someone sent a drive by patch to
> some driver they'll start showing up in the git history and often get
> CCed on future changes going forwards, which can then result in getting
> copied into further postings done by copying from prior postings.  That
> does feel somewhat tractable to education, at least in the early stages.

And for drive-by changes to Kconfig files or Makefiles, it is amplified
to any other sections in these files :-(

Perhaps scripts/get_maintainer.pl can be taught to only consider the
subsystem maintainer, and ignore git history, for changes to Makefiles
and Kconfig files?

Or move the Kconfig/Makefile bits into the driver sources, next to
the MODULE_*() bits, which I believe was part of Roman Zippel's big
plan when he wrote the new Kconfig system...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds