From: "Serge E. Hallyn" <serge@hallyn.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: 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, Lee Jones <lee@kernel.org>
Subject: Re: Validating MAINTAINERS entries?
Date: Wed, 10 Aug 2022 07:12:41 -0500 [thread overview]
Message-ID: <20220810121241.GA6146@mail.hallyn.com> (raw)
In-Reply-To: <20220810120450.GT3460@kadam>
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.
>
> When I send patches, there are few people that I know what they're about
> and I manually delete them. I also know which mailing lists those
> people read so normally they're going to get the email even if they're
> not on the CC list.
>
> Other times, I wonder why maintainers are still on the CC list if they
> haven't been active in years. But I'm not going to manually remove
> them. It's worse to get chewed out for not CCing someone than for
> including them.
Huh. Chewed out for including them? I had always thought that was *the*
point of MAINTAINERS.
Now, with lei (<3), MAINTAINERS becomes less important, as I can search
for the files/functions I'm interested in, and until someone starts
sending spam including patch hunks just to get pulled into such searches
that's more reliable than my shoddy spam filtering attempts on personal
email :) The latter dropping important emails and letting through spam...
> The one split which is quite confusing to me is the netdev vs wireless
> split. For wireless patches, I generelly delete all the netdev
> maintainers. Some people I'm not sure what they care about so I leave
> them.
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2022-08-10 12:19 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 [this message]
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
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=20220810121241.GA6146@mail.hallyn.com \
--to=serge@hallyn.com \
--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