From: Bagas Sanjaya <bagasdotme@gmail.com>
To: James Seo <james@equiv.tech>, Jonathan Corbet <corbet@lwn.net>
Cc: 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 21:01:29 +0700 [thread overview]
Message-ID: <10e68064-42a3-c80e-10cc-079a3cf4eb35@gmail.com> (raw)
In-Reply-To: <20230603151447.29288-1-james@equiv.tech>
On 6/3/23 22:14, James Seo wrote:
> To reduce ambiguity and eliminate this class of potential (albeit
> tangential) issues, prescribe sending patches 'To' maintainers and
> 'Cc' lists. While we're at it, strengthen the recommendation to use
> scripts/get_maintainer.pl to find patch recipients, and move Andrew
> Morton's callout as the maintainer of last resort to the next
> paragraph for better flow.
>
IMO, To: and Cc: don't have any practical differences between two,
and I usually do vice-versa when sending patches: lists are in To:
and individual maintainers are in Cc:
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-06-04 14:01 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
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 [this message]
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=10e68064-42a3-c80e-10cc-079a3cf4eb35@gmail.com \
--to=bagasdotme@gmail.com \
--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=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