Skip to content

Commit 2f99350

Browse files
knurdJonathan Corbet
authored andcommitted
docs: process/5.Posting.rst: clarify use of Reported-by: tag
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 <[email protected]> Link: https://lore.kernel.org/r/2fc7162dfb76e04da5ea903c9c170d913e735dad.1664372256.git.linux@leemhuis.info Signed-off-by: Jonathan Corbet <[email protected]>
1 parent e94102e commit 2f99350

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

Documentation/process/5.Posting.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -256,8 +256,10 @@ The tags in common use are:
256256
- Cc: the named person received a copy of the patch and had the
257257
opportunity to comment on it.
258258

259-
Be careful in the addition of tags to your patches: only Cc: is appropriate
260-
for addition without the explicit permission of the person named.
259+
Be careful in the addition of tags to your patches, as only Cc: is appropriate
260+
for addition without the explicit permission of the person named; using
261+
Reported-by: is fine most of the time as well, but ask for permission if
262+
the bug was reported in private.
261263

262264

263265
Sending the patch

0 commit comments

Comments
 (0)