* [PATCH v1] docs: process/5.Posting.rst: clarify use of Reported-by: tag
@ 2022-09-28 13:39 Thorsten Leemhuis
2022-09-29 19:11 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Leemhuis @ 2022-09-28 13:39 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-doc, Linux Kernel Mailing List
Bring the description on when to use the Reported-by: tag found in
Documentation/process/5.Posting.rst more in line with the description in
Documentation/process/submitting-patches.rst: before this change the two
were contradicting each other, as the latter is way more permissive and
only states '[...] if the bug was reported in private, then ask for
permission first before using the Reported-by tag.'
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
Hi! I noticed some confusion in our development community on when to use
the Reported-by: tag. Some of this apparently is caused by the
inconsistency fixed in this patch. Ciao, Thorsten
---
Documentation/process/5.Posting.rst | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst
index 906235c11c24..d87f1fee4cbc 100644
--- a/Documentation/process/5.Posting.rst
+++ b/Documentation/process/5.Posting.rst
@@ -256,8 +256,10 @@ The tags in common use are:
- Cc: the named person received a copy of the patch and had the
opportunity to comment on it.
-Be careful in the addition of tags to your patches: only Cc: is appropriate
-for addition without the explicit permission of the person named.
+Be careful in the addition of tags to your patches, as only Cc: is appropriate
+for addition without the explicit permission of the person named; using
+Reported-by: is fine most of the time as well, but ask for permission if
+the bug was reported in private.
Sending the patch
base-commit: 3ef859a4f6c97253b75eb53d259b7789fb92d875
--
2.37.3
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v1] docs: process/5.Posting.rst: clarify use of Reported-by: tag
2022-09-28 13:39 [PATCH v1] docs: process/5.Posting.rst: clarify use of Reported-by: tag Thorsten Leemhuis
@ 2022-09-29 19:11 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2022-09-29 19:11 UTC (permalink / raw)
To: Thorsten Leemhuis; +Cc: linux-doc, Linux Kernel Mailing List
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Bring the description on when to use the Reported-by: tag found in
> Documentation/process/5.Posting.rst more in line with the description in
> Documentation/process/submitting-patches.rst: before this change the two
> were contradicting each other, as the latter is way more permissive and
> only states '[...] if the bug was reported in private, then ask for
> permission first before using the Reported-by tag.'
>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
>
> ---
> Hi! I noticed some confusion in our development community on when to use
> the Reported-by: tag. Some of this apparently is caused by the
> inconsistency fixed in this patch. Ciao, Thorsten
> ---
> Documentation/process/5.Posting.rst | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-09-29 19:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-09-28 13:39 [PATCH v1] docs: process/5.Posting.rst: clarify use of Reported-by: tag Thorsten Leemhuis
2022-09-29 19:11 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).