From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: corbet@lwn.net, konstantin@linuxfoundation.org,
krzysztof.kozlowski@linaro.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@leemhuis.info, tytso@mit.edu
Subject: Re: [PATCH v3] Documentation/process: Add text to indicate supporters should be mailed
Date: Fri, 30 Sep 2022 17:34:23 +0100 [thread overview]
Message-ID: <2be9c226-fe38-20f3-d620-6ea57d168c33@linaro.org> (raw)
In-Reply-To: <b119fee5-807f-1940-3378-f5ad638794f5@linaro.org>
On 30/09/2022 17:18, Bryan O'Donoghue wrote:
> 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?
Ah I see you are suggesting a document not a get_maintainer.pl edit, my
mistake.
Yes, I'm fine to change the text to something like this if you feel it
reads better that way.
I'd still appreciate some more eloboration/rationale on what you don't
like about giving an example.
Is it the example in general you dislike ? Personally I find an example
a useful thing but, that's just a personal preference.
---
bod
next prev parent reply other threads:[~2022-09-30 16:34 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 [this message]
2022-10-01 2:37 ` Theodore Ts'o
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=2be9c226-fe38-20f3-d620-6ea57d168c33@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=akiyks@gmail.com \
--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 \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®