All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Carpenter <dan.carpenter@oracle.com>, Rob Landley <rob@landley.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Paul Bolle <pebolle@tiscali.nl>,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [patch] Documentation/SubmittingPatches: Reported-by tags and permission
Date: Fri, 14 Feb 2014 15:34:31 -0800	[thread overview]
Message-ID: <52FEA807.9040100@infradead.org> (raw)
In-Reply-To: <20140214093001.GA15933@elgon.mountain>

On 02/14/2014 01:30 AM, Dan Carpenter wrote:
> The reported-by text says you have to ask for permission, but that's
> only if the bug was reported in private.  These days the standard is to
> always give reported-by credit or it's considered a bit rude.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 26b1e31d5a13..f72ce7803b71 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -432,12 +432,9 @@ have been included in the discussion
>  
>  14) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-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.
> +The Reported-by tag is to give credit to people who find bugs and report them.
> +Please note that if the bug was reported in private, then ask for permission
> +first before using the Reported-by tag.
>  
>  A Tested-by: tag indicates that the patch has been successfully tested (in
>  some environment) by the person named.  This tag informs maintainers that
> --


-- 
~Randy

  reply	other threads:[~2014-02-14 23:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 12:31 [PATCH] staging: r8188eu: default to "y" in Kconfig Paul Bolle
2014-02-11 12:53 ` Dan Carpenter
2014-02-11 13:01   ` Paul Bolle
2014-02-11 13:17     ` Dan Carpenter
2014-02-13 23:22       ` Paul Bolle
2014-02-14  9:30         ` [patch] Documentation/SubmittingPatches: Reported-by tags and permission Dan Carpenter
2014-02-14 23:34           ` Randy Dunlap [this message]
2014-10-28 13:04           ` Jonathan Corbet
2014-10-28 16:58             ` Jason Cooper
2014-10-28 17:41               ` Jonathan Corbet
2014-10-29 10:01             ` [patch v2] " Dan Carpenter
2014-10-29 12:57               ` Jonathan Corbet
2014-10-29 15:50               ` Rob Landley
2014-02-12  0:09 ` [PATCH] staging: r8188eu: default to "y" in Kconfig Martin Walch
2014-02-12  0:25   ` Paul Bolle
2014-02-12  0:37     ` Paul Bolle

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=52FEA807.9040100@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.