From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Willy Tarreau <w@1wt.eu>, Randy Dunlap <rdunlap@infradead.org>,
James Seo <james@equiv.tech>, Jonathan Corbet <corbet@lwn.net>,
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: Tue, 06 Jun 2023 16:46:25 +0300 [thread overview]
Message-ID: <87ilc0itzi.fsf@kernel.org> (raw)
In-Reply-To: <20230605103029.3fb821db@kernel.org> (Jakub Kicinski's message of "Mon, 5 Jun 2023 10:30:29 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> On Mon, 05 Jun 2023 16:22:46 +0300 Kalle Valo wrote:
>> > Note that some maintainers process pull requests from patchwork, not
>> > from their mailbox, and prefer not to be aadressed in the To or CC
>> > headers. I don't know how widespread that is.
>>
>> FWIW I belong to this group and prefer not be in To or Cc, I'll always
>> check the patch from patchwork.
>
> Ah, I didn't realize this.
So no action needed for this, I'm sure I'm in a very small minority and
I can handle the mails with my filters just fine. Just wanted to comment
that such maintainers do exist.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-06-06 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 15:14 [RFC] docs: process: Send patches 'To' maintainers and 'Cc' lists James Seo
2023-06-03 15:55 ` Randy Dunlap
2023-06-03 16:06 ` Willy Tarreau
2023-06-04 18:26 ` Jakub Kicinski
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 [this message]
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=87ilc0itzi.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=corbet@lwn.net \
--cc=james@equiv.tech \
--cc=kuba@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).