public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Cashin <ecashin@coraid.com>
From: Ed Cashin <ecashin@coraid.com>
To: rob@landley.net
Cc: linux-doc@vger.kernel.org, ecashin@coraid.com,
	dan.carpenter@oracle.com, kernel-janitors@vger.kernel.org,
	corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation/SubmittingPatches: implicit permission for public reports
Date: Wed, 24 Oct 2012 10:22:02 -0400	[thread overview]
Message-ID: <623a994357ba3348d5a4a0a2003b4dc0@coraid.com> (raw)

The current text of SubmittingPatches recommends asking permission
before using "Reported-By:" even when the report was made to a
public forum.  This patch updates the text to better reflect the
current convention of including the tag when the report was public.

Signed-off-by: Ed Cashin <ecashin@coraid.com>
---
 Documentation/SubmittingPatches |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index c379a2a..d30b692 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -423,12 +423,12 @@ have been included in the discussion
 
 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.
+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 unless the problem was 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
-- 
1.7.1


             reply	other threads:[~2012-10-24 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 14:22 Ed Cashin, Ed Cashin [this message]
2012-10-24 14:36 ` [PATCH] Documentation/SubmittingPatches: implicit permission for public reports Jonathan Corbet
2012-10-24 14:40   ` Ed Cashin

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=623a994357ba3348d5a4a0a2003b4dc0@coraid.com \
    --to=ecashin@coraid.com \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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