From: Jakub Kicinski <kuba@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Randy Dunlap <rdunlap@infradead.org>,
James Seo <james@equiv.tech>, Jonathan Corbet <corbet@lwn.net>,
Kalle Valo <kvalo@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] docs: process: Send patches 'To' maintainers and 'Cc' lists
Date: Sun, 4 Jun 2023 11:26:44 -0700 [thread overview]
Message-ID: <20230604112644.49ac2035@kernel.org> (raw)
In-Reply-To: <20230603160659.GA5182@1wt.eu>
On Sat, 3 Jun 2023 18:06:59 +0200 Willy Tarreau wrote:
> > I think that is going overboard (too far). As long as a maintainer
> > is a direct recipient of the email (patch), that should be sufficient.
>
> Or it could be simplified, saying that all those who are expected to
> play a role on the patchset (review, test, merge etc) should be in the
> 'To' field while those who might possibly be interested in having a
> look are in 'Cc' (lists, other people having expressed interest in the
> patchset, single-time contributors to the file being changed etc). It
> could be hinted that usually people read mails sent to them faster than
> those they're CCed. This implies that maintainers have to be in To and
> lists in Cc.
It's useful when maintainer (or group thereof) who are expected to apply
the patch are in the To:
Who applies the patch is not information a noob may know but it may be
worth writing down as best practice?
next prev parent reply other threads:[~2023-06-04 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 15:14 James Seo
2023-06-03 15:55 ` Randy Dunlap
2023-06-03 16:06 ` Willy Tarreau
2023-06-04 18:26 ` Jakub Kicinski [this message]
2023-06-05 4:12 ` Laurent Pinchart
2023-06-05 13:22 ` Kalle Valo
2023-06-05 17:30 ` Jakub Kicinski
2023-06-06 13:46 ` Kalle Valo
2023-06-04 13:56 ` Bagas Sanjaya
2023-06-04 14:01 ` Bagas Sanjaya
2023-06-04 21:53 ` Randy Dunlap
2023-06-04 18:33 ` Jakub Kicinski
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=20230604112644.49ac2035@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=james@equiv.tech \
--cc=kvalo@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=w@1wt.eu \
--cc=workflows@vger.kernel.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