Re: Validating MAINTAINERS entries?

[Lee Jones <lee@kernel.org>]

On Wed, 10 Aug 2022, Rob Herring wrote:

> On Wed, Aug 10, 2022 at 7:25 AM Lee Jones <lee@kernel.org> wrote:
> >
> > On Wed, 10 Aug 2022, Mark Brown 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.
> 
> After your W=1 and kerneldoc fixes, you're screwed. ;)

Yes, and the tragic thing is, I still have aspirations to go finish that!

> > > > > Or is this just an education point?
> > >
> > > > Education is not the answer.
> 
> Yes. I'm convinced there is no way to solve these problems on the
> sender side. I see plenty of cases of not running get_maintainers.pl.
> You've got to filter out what you want on your end. And lei is great
> for that.
> 
> > > > 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.
> >
> > How about default tooling values, get_maintainer.pl in this case?
> >
> > I tend to over-ride this default to 75% to avoid the aforementioned:
> >
> >   --git-min-percent => minimum percentage of commits required (default: 5)
> >
> > 5 is not a lot of percent for seldomly touched source files.
> 
> Send a patch. I would also bump --git-min-signatures from 1.

I can do that.  Fair warning, it won't be until around mid-cycle.

-- 
Lee Jones [李琼斯]