From: Greg KH <gregkh@linuxfoundation.org>
To: john ashrith6 <johnashrith6@gmail.com>
Cc: workflows@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: clarify CC list guidance wording
Date: Sun, 25 Jan 2026 15:39:21 +0100 [thread overview]
Message-ID: <2026012556-majestic-traitor-8f03@gregkh> (raw)
In-Reply-To: <CABoKZACHObTMAC5FMvhRG3Guev_s_Pys_t3G7LAqF7BTiLD+KQ@mail.gmail.com>
On Sun, Jan 25, 2026 at 08:08:08PM +0530, john ashrith6 wrote:
> This patch clarifies wording in the CC list guidance to avoid ambiguity.
>
> No functional changes intended.
>
> >From 416237c2cea7ccb4fa863ebc260777ea102b2b62 Mon Sep 17 00:00:00 2001
> From: JAR2004re <johnashrith6@gmail.com>
> Date: Sun, 25 Jan 2026 14:17:13 +0000
> Subject: [PATCH] docs: clarify CC list guidance wording
No need for this to be in the body of the email/changelog.
> Signed-off-by: JAR2004re <johnashrith6@gmail.com>
Please use your name here, not your alias.
thanks,
greg k-h
prev parent reply other threads:[~2026-01-25 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 14:38 john ashrith6
2026-01-25 14:39 ` Greg KH [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=2026012556-majestic-traitor-8f03@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=johnashrith6@gmail.com \
--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