From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
linux@leemhuis.info, konstantin@linuxfoundation.org,
krzysztof.kozlowski@linaro.org, linux-doc@vger.kernel.org,
joe@perches.com
Subject: Re: [PATCH v5 1/1] Documentation/process: Be more explicit about who to mail on patch submission
Date: Tue, 4 Oct 2022 17:38:27 +0100 [thread overview]
Message-ID: <8042912e-23a8-d32e-1aae-fb766ecb865a@linaro.org> (raw)
In-Reply-To: <42f15689-d1ad-2be8-5fed-8f72d82402dc@linaro.org>
On 04/10/2022 17:27, Bryan O'Donoghue wrote:
> You are not _required_ to run get_maintainer to submit a patch, it is
> simply _suggested_ so in my view the output of get_maintainer doesn't
> negate the statement that you must mail at least one public mailing list.
And similarly, saying in a subsequent paragraph that you should always
mail at last one public mailing list is unnecessarily disregarding
information returned by get_maintainer.
get_maintainer produces a list of text that is very helpful to a
developer in deciding where to send a patch. Documenting that output
directly is a help.
But unless/until get_maintainer is _required_ to be run on any given
patch, then we should still have a standalone paragraph which explicitly
states a public mailing list must receive the patch.
---
bod
next prev parent reply other threads:[~2022-10-04 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 12:48 [PATCH v5 0/1] Fixup instructions around mailing recipients Bryan O'Donoghue
2022-10-04 12:48 ` [PATCH v5 1/1] Documentation/process: Be more explicit about who to mail on patch submission Bryan O'Donoghue
2022-10-04 15:17 ` Akira Yokosawa
2022-10-04 16:27 ` Bryan O'Donoghue
2022-10-04 16:38 ` Bryan O'Donoghue [this message]
2022-10-06 14:22 ` Akira Yokosawa
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=8042912e-23a8-d32e-1aae-fb766ecb865a@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--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;
as well as URLs for NNTP newsgroup(s).