From: Jonathan Corbet <corbet@lwn.net>
To: John Ashrith <johnashrith6@gmail.com>, workflows@vger.kernel.org
Cc: gregkh@linuxfoundation.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4] docs: clarify CC list guidance wording
Date: Sun, 25 Jan 2026 11:40:29 -0700 [thread overview]
Message-ID: <87ecndedsy.fsf@trenco.lwn.net> (raw)
In-Reply-To: <0bb5ad12-dd5a-4280-bf6e-7d1ddb59dd9e@gmail.com>
John Ashrith <johnashrith6@gmail.com> writes:
> Changes since v3:
> - Add proper changelog text
> - Move version notes below the --- line
> - Send as plain text to avoid mail client mangling
>
> From 1de01779d580e104bea0148409c3c8c76d204c41 Mon Sep 17 00:00:00 2001
> From: John Ashrith <johnashrith6@gmail.com>
> Date: Sun, 25 Jan 2026 14:48:28 +0000
> Subject: [PATCH] docs: clarify CC list guidance wording
Again ... the above text should not be in the changelog. I can
certainly edit it out on applying the patch, but you really need to find
a way to send patches that don't make maintainers do extra work.
I'll say again: please practice sending to yourself until this comes out
right, then resend your patch to the lists.
Thanks,
jon
next prev parent reply other threads:[~2026-01-25 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 16:21 John Ashrith
2026-01-25 18:40 ` Jonathan Corbet [this message]
2026-01-26 4:22 John Ashrith
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=87ecndedsy.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=johnashrith6@gmail.com \
--cc=linux-doc@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