From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Manuel Ebner <manuelebner@mailbox.org>,
Shuah Khan <skhan@linuxfoundation.org>,
"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [Question] 5.posting.rst use To: or Cc:
Date: Mon, 22 Jun 2026 16:15:29 +0200 [thread overview]
Message-ID: <6ba29d12-a50d-4bc6-8276-cf1300d3d671@kernel.org> (raw)
In-Reply-To: <87ik7o9bj0.fsf@trenco.lwn.net>
On 12/06/2026 14:41, Jonathan Corbet wrote:
> Manuel Ebner <manuelebner@mailbox.org> writes:
>
>> so every time I send a mail to lists or maintainers I have to choose: To:
>> or Cc:. I did look for an answer in the Documentation but couldn't find
>> one.
>> I think if there is an answer then it could be added to 5.posting.rst .
>
> Normally you would To: the maintainers, CC: the rest, but the end result
> is the same either way - it really doesn't matter.
>
Yes and 'b4' follows that logic. I think I saw only one case when
maintainer relied on actual To/Cc difference, but it was pointed out
that it is fragile and there is no unified rule.
Regardless, just use b4 to contribute patches because it solves all such
process issues. And whenever process is different, we tend to
fix/improve b4 to implement it correctly or we should change the
process, because in general we should not have rules which cannot be
implemented in toolset.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-06-22 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 8:01 [Question] 5.posting.rst use To: or Cc: Manuel Ebner
2026-06-12 12:41 ` Jonathan Corbet
2026-06-22 14:15 ` Krzysztof Kozlowski [this message]
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=6ba29d12-a50d-4bc6-8276-cf1300d3d671@kernel.org \
--to=krzk@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebner@mailbox.org \
--cc=skhan@linuxfoundation.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