[PATCH v4] docs: clarify CC list guidance wording

[PATCH v4] docs: clarify CC list guidance wording

[John Ashrith]

 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

Clarify that recipients should not be removed from the CC list without a
good reason, and that replies should not be sent only to the list address.
This avoids ambiguity in the guidance.

Signed-off-by: John Ashrith <johnashrith6@gmail.com>
---
v4:
- Add changelog text to the commit message
- Ensure patch is sent as text/plain without mail client mangling
- Place version notes below the --- line

  Documentation/process/howto.rst | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/process/howto.rst 
b/Documentation/process/howto.rst
index 9438e03d6..5a29111d6 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -403,7 +403,7 @@ interacting with the list (or any list):

  If multiple people respond to your mail, the CC: list of recipients may
  get pretty large. Don't remove anybody from the CC: list without a good
-reason, or don't reply only to the list address. Get used to receiving the
+reason, and don't reply only to the list address. Get used to receiving the
  mail twice, one from the sender and the one from the list, and don't try
  to tune that by adding fancy mail-headers, people will not like it.

--
2.43.0

[PATCH v4] docs: clarify CC list guidance wording

[John Ashrith]

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

Clarify that recipients should not be removed from the CC list without a
good reason, and that replies should not be sent only to the list address.
This avoids ambiguity in the guidance.

Signed-off-by: John Ashrith <johnashrith6@gmail.com>
---
v4:
- Add changelog text to the commit message
- Ensure patch is sent as text/plain without mail client mangling
- Place version notes below the --- line

  Documentation/process/howto.rst | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/process/howto.rst 
b/Documentation/process/howto.rst
index 9438e03d6..5a29111d6 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -403,7 +403,7 @@ interacting with the list (or any list):

  If multiple people respond to your mail, the CC: list of recipients may
  get pretty large. Don't remove anybody from the CC: list without a good
-reason, or don't reply only to the list address. Get used to receiving the
+reason, and don't reply only to the list address. Get used to receiving the
  mail twice, one from the sender and the one from the list, and don't try
  to tune that by adding fancy mail-headers, people will not like it.

--
2.43.0

Re: [PATCH v4] docs: clarify CC list guidance wording

[Jonathan Corbet]

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