projects
/
linux-block.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
126437f
)
docs: 5.Posting: mentioned Suggested-by: tag
author
Thorsten Leemhuis
<linux@leemhuis.info>
Mon, 2 Dec 2024 08:12:19 +0000
(09:12 +0100)
committer
Jonathan Corbet
<corbet@lwn.net>
Wed, 11 Dec 2024 16:07:40 +0000
(09:07 -0700)
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@linuxfoundation.org>
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link:
https://lore.kernel.org/r/fbebad6605b02e372b24c2cfa1e05f789fed43d1.1733127086.git.linux@leemhuis.info
Documentation/process/5.Posting.rst
patch
|
blob
|
blame
|
history
diff --git
a/Documentation/process/5.Posting.rst
b/Documentation/process/5.Posting.rst
index b3eff03ea2491c887050d97a1a6e97054a948bec..dbb763a8de901dee6f9b2a37d1177090057eecbb 100644
(file)
--- 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.