ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee@kernel.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	 Lee Jones <lee.jones@linaro.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>, Greg KH <greg@kroah.com>,
	 Stephen Hemminger <stephen@networkplumber.org>,
	ksummit@lists.linux.dev
Subject: Re: Validating MAINTAINERS entries?
Date: Wed, 10 Aug 2022 08:20:32 -0600	[thread overview]
Message-ID: <CAL_JsqJH41LZQvtiJMn_70FQLzjq=8aNOX3qymjPf6+0rwxodQ@mail.gmail.com> (raw)
In-Reply-To: <YvO6LY3kE02/uvXe@sirena.org.uk>

On Wed, Aug 10, 2022 at 8:01 AM Mark Brown <broonie@kernel.org> wrote:
>
> On Wed, Aug 10, 2022 at 07:54:59AM -0600, 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:
>
> > > > > 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.
>
> We can't solve problems, but we can make things a bit better.
>
> > You've got to filter out what you want on your end. And lei is great
> > for that.
>
> lei is too new for Debian stable :/

Meaning it's not packaged or needs newer dependencies?

> > >   --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.
>
> Will that do the right thing in cases like recently added files?

Yes, because I'm sure checkpatch.pl was run on the patch adding the
files and it tells you 'added file, need a MAINTAINERS entry?'.

Really, I would (and do) turn off gitfallback completely by default.
If someone wants to be CCed and there's not a MAINTAINERS entry, then
that's on them.

Rob

  parent reply	other threads:[~2022-08-10 14:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10  0:13 Stephen Hemminger
2022-08-10  8:23 ` Greg KH
2022-08-10  8:26 ` Dan Carpenter
2022-08-10  8:36   ` Greg KH
2022-08-10  8:55     ` Lukas Bulwahn
2022-08-10  9:10       ` Dan Carpenter
2022-08-10 11:50       ` Lee Jones
2022-08-10 12:04         ` Dan Carpenter
2022-08-10 12:12           ` Serge E. Hallyn
2022-08-10 12:50           ` Mark Brown
2022-08-10 13:25             ` Lee Jones
2022-08-10 13:54               ` Rob Herring
2022-08-10 14:01                 ` Mark Brown
2022-08-10 14:19                   ` Konstantin Ryabitsev
2022-08-10 14:20                   ` Rob Herring [this message]
2022-08-10 14:35                     ` Mark Brown
2022-08-11 12:36                       ` Sudip Mukherjee
2022-08-10 15:29                 ` Lee Jones
2022-08-11  8:35             ` Geert Uytterhoeven
2022-08-11  8:42               ` Christoph Hellwig
2022-08-10  8:46   ` Lukas Bulwahn
2022-08-10  8:42 ` Lukas Bulwahn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL_JsqJH41LZQvtiJMn_70FQLzjq=8aNOX3qymjPf6+0rwxodQ@mail.gmail.com' \
    --to=robherring2@gmail.com \
    --cc=broonie@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=greg@kroah.com \
    --cc=ksummit@lists.linux.dev \
    --cc=lee.jones@linaro.org \
    --cc=lee@kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox