[<prev] [next>] [day] [month] [year] [list]
Message-ID: <fbebad6605b02e372b24c2cfa1e05f789fed43d1.1733127086.git.linux@leemhuis.info>
Date: Mon, 2 Dec 2024 09:12:19 +0100
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Jonathan Corbet <corbet@....net>
Cc: workflows@...r.kernel.org,
linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: [PATCH v3] docs: 5.Posting: mentioned Suggested-by: tag
Mention the Suggested-by: tag in 5.Posting.rst in a way similar to
submitting-patches.rst, which according to the header of the latter is
the less detailed document of the two.
Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
---
v3:
- first version, split out from another patch-set that was at v2:
https://lore.kernel.org/all/1609d461030094b294f08d0b4e208d32993ac799.1731749544.git.linux@leemhuis.info/
- add Reviewed-by: from Greg
---
Documentation/process/5.Posting.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst
index b3eff03ea2491c..dbb763a8de901d 100644
--- a/Documentation/process/5.Posting.rst
+++ b/Documentation/process/5.Posting.rst
@@ -261,6 +261,10 @@ The tags in common use are:
can be used instead of Closes: if the patch fixes a part of the issue(s)
being reported.
+ - A Suggested-by: tag indicates that the patch idea is suggested by the person
+ named and ensures credit to the person for the idea. This will, hopefully,
+ inspire them to help us again in the future.
+
- Cc: the named person received a copy of the patch and had the
opportunity to comment on it.
base-commit: 83a474c11e8cb59e230a43365cb42fa00d3bddaa
--
2.45.0
Powered by blists - more mailing lists