lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 29 Oct 2014 10:50:42 -0500
From:	Rob Landley <rob@...dley.net>
To:	Dan Carpenter <dan.carpenter@...cle.com>,
	Jonathan Corbet <corbet@....net>
CC:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Paul Bolle <pebolle@...cali.nl>, devel@...verdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [patch v2] Documentation/SubmittingPatches: Reported-by tags
 and permission

On 10/29/14 05:01, Dan Carpenter wrote:
> The reported-by text says you have to ask for permission, but that
> should only be 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@...cle.com>
> 
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 482c749..1fa1caa 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -483,12 +483,10 @@ have been included in the discussion
>  
>  14) Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes:
>  
> -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 gives credit to people who find bugs and report them and it
> +hopefully inspires them to help us again in the future.  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

Nitpick: no colon at end of tag name?

Rob

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ