From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reported-by (Re: Fix a typo in the development process document.)
Date: Thu, 15 Jan 2009 15:59:05 -0700 [thread overview]
Message-ID: <20090115155905.36abc28e@bike.lwn.net> (raw)
In-Reply-To: <20090109151535.336c3afd.randy.dunlap@oracle.com>
On Fri, 9 Jan 2009 15:15:35 -0800
Randy Dunlap <randy.dunlap@oracle.com> 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
Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index f309d3c..6f29e29 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -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
prev parent reply other threads:[~2009-01-15 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901090059.n090xfIH030955@hera.kernel.org>
2009-01-09 23:15 ` Randy Dunlap
2009-01-15 22:59 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090115155905.36abc28e@bike.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®