Skip to contentSkip to conversation

Reported-by (Re: Fix a typo in the development process document.)

DISCUSSION Randy Dunlap 2 participants 2 messages Jan 9, 2009 – Jan 15, 2009 1 message not in the archive Documentation

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 8 lines · On Fri, 9 Jan 2009 00:59:41 GMT Linux Kernel Mailing List wrote:
Gitweb:     http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d5b524327b2a482dddae3839ced8f8825074730d
Commit:     d5b524327b2a482dddae3839ced8f8825074730d
Parent:     2884f00b94be73a6a7875bada739bf9bb2f9a1b6
Author:     Jonathan Corbet <[email protected]>
AuthorDate: Thu Jan 8 16:32:13 2009 -0700
Committer:  Jonathan Corbet <[email protected]>
CommitDate: Thu Jan 8 16:32:13 2009 -0700
Quoted 4 lines

Fix a typo in the development process document.

BTW, Jon, if Reported-by: is supposed to have a status that is (nearly) as well accepted as most of the other tags, then it should be documented in SubmittingPatches along with the other tags and not only in development-process/5.Posting, no?

Or maybe it's not as well accepted as the others...
http://www.remword.com/kps_result/2_6_29_report.html

---
~Randy

maintainer
#2 lore raw
Quoted 4 lines · On Fri, 9 Jan 2009 15:15:35 -0800 Randy Dunlap <[email protected]> wrote:

BTW, Jon, if Reported-by: is supposed to have a status that is (nearly) as well accepted as most of the other tags, then it should be documented in SubmittingPatches along with the other tags and not only in development-process/5.Posting, no?

Yes, it probably should. How's the following? I'll drop it into my docs tree if nobody gripes.

jon

--

Document Reported-by: in SubmittingPatches

Documentation/SubmittingPatches +8 -1
index f309d3c..6f29e29 100644
@@ -405,7 +405,14 @@ person it names.  This tag documents that potentially interested parties
 have been included in the discussion
 
 
-14) Using Tested-by: and Reviewed-by:
+14) Using Reported-by:, Tested-by: and Reviewed-by:
+
+If this patch fixes a problem reported by somebody else, consider adding a
+Reported-by: tag to credit the reporter for their contribution.  Please
+note that this tag should not be added without the reporter's permission,
+especially if the problem was not reported in a public forum.  That said,
+if we diligently credit our bug reporters, they will, hopefully, be
+inspired to help us again in the future.
 
 A Tested-by: tag indicates that the patch has been successfully tested (in
 some environment) by the person named.  This tag informs maintainers that