public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: Akira Yokosawa <akiyks@gmail.com>,
	corbet@lwn.net, konstantin@linuxfoundation.org,
	krzysztof.kozlowski@linaro.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux@leemhuis.info
Subject: Re: [PATCH v3] Documentation/process: Add text to indicate supporters should be mailed
Date: Fri, 30 Sep 2022 22:37:21 -0400	[thread overview]
Message-ID: <Yzen4X1Na0MKXHs9@mit.edu> (raw)
In-Reply-To: <b119fee5-807f-1940-3378-f5ad638794f5@linaro.org>

On Fri, Sep 30, 2022 at 05:18:52PM +0100, Bryan O'Donoghue wrote:
> > So the root cause of your confusion was you couldn't figure out
> > the fact that "supporter" in the output of get_maintainver.pl means
> > "maintainer of a supported subsystem", wasn't it?
> > 
> > I guess all you need would be just a short notice along the lines of:
> > 
> >      "supporter" in the output from get_maintainer.pl means "maintainer
> >      of a supported subsystem".
> > 
> > No?
> 
> We discussed that a bit earlier.
> 
> https://lore.kernel.org/lkml/20220928003006.230103-1-bryan.odonoghue@linaro.org/T/#u
> https://lkml.org/lkml/2022/9/28/1394
> https://lkml.org/lkml/2022/9/28/1511
> https://lkml.org/lkml/2022/9/29/188
> 
> I think its fair to say the consensus so far is to leave the
> get_maintainer.pl output as is.


FWIW, I actually think the output of get_maintainer.pl is pretty
broken in this regard.  (Then again, I've never thought all that
highly of get_maintainer.pl, *especially* because of the bogus git
fallback, but that's another story.)

Consider:

% ./scripts/get_maintainer.pl --file  drivers/acpi/power.c
"Rafael J. Wysocki" <rafael@kernel.org> (supporter:ACPI)
Len Brown <lenb@kernel.org> (reviewer:ACPI)
linux-acpi@vger.kernel.org (open list:ACPI)
linux-kernel@vger.kernel.org (open list)

I'm sorry, but that's just *wrong*.  Rafael is the *maintainer* of the
ACPI subsystem, and the term "supporter" is rarely if ever used
anywhere in our docs.  As I said earlier, trying to treat S: field to
say anything about the entitles listed under the M: field of the
Maintainers file is a category error.

Consider: ACPI subsystem is is "supported".  From a user's
perspective, what are they supposed to take from that?  That the ACPI
subsystem is somehow better supported than say, the MM subsystem
(which is only "maintained"), or all of Linux networking, which is
also "maintained".  And so Rafel is a "supporter", but David Miller
and Andrew Morton are "maintainers", respectively. ?!?

I think the original rationale behind the S: field is to help people
understand, in particular for device drivers, how solid a particular
device driver might be.  Was it officially supported by the hardware
manufacturer?  Was it supported by a some random student who hacked
something together?  Was the still being actively maintained?  But
even then, just because a driver is "officially" supported by the
hardware manufacturer doesn't necessarily mean that it is any more
reliable, or high quality, than something which is being supported by
someone who supposedly isn't getting paid to support it.  (And there
are plenty of subsystems listed as "maintained" where the people
listed under M: are most certainly getting paid to work on it.)

       	     	    	 	   	   - Ted

  parent reply	other threads:[~2022-10-01  2:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  6:46 [PATCH v3 0/1] Expand get_maintainer to be explicit about supporters Bryan O'Donoghue
2022-09-30  6:46 ` [PATCH v3] Documentation/process: Add text to indicate supporters should be mailed Bryan O'Donoghue
2022-09-30 14:47   ` Akira Yokosawa
2022-09-30 16:18     ` Bryan O'Donoghue
2022-09-30 16:34       ` Bryan O'Donoghue
2022-10-01  2:37       ` Theodore Ts'o [this message]
2022-10-01 10:37         ` Bryan O'Donoghue
2022-10-02  0:27           ` Akira Yokosawa
2022-10-02  7:58           ` Krzysztof Kozlowski
2022-10-02 15:49             ` Joe Perches
2022-10-02 23:04               ` Akira Yokosawa
2022-10-02 23:55                 ` Joe Perches
2022-10-03  1:17                   ` Akira Yokosawa
2022-10-03  1:28                     ` Joe Perches
2022-09-30 18:41     ` Bryan O'Donoghue

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=Yzen4X1Na0MKXHs9@mit.edu \
    --to=tytso@mit.edu \
    --cc=akiyks@gmail.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=corbet@lwn.net \
    --cc=konstantin@linuxfoundation.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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