linux-kernel - Re: [PATCH v1] docs: process/5.Posting.rst: clarify use of Reported-by: tag

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]

Message-ID: <87a66ihu76.fsf@meer.lwn.net>
Date:   Thu, 29 Sep 2022 13:11:25 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Thorsten Leemhuis <linux@...mhuis.info>
Cc:     linux-doc@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] docs: process/5.Posting.rst: clarify use of
 Reported-by: tag

Thorsten Leemhuis <linux@...mhuis.info> writes:

> Bring the description on when to use the Reported-by: tag found in
> Documentation/process/5.Posting.rst more in line with the description in
> Documentation/process/submitting-patches.rst: before this change the two
> were contradicting each other, as the latter is way more permissive and
> only states '[...] if the bug was reported in private, then ask for
> permission first before using the Reported-by tag.'
>
> Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
>
> ---
> Hi! I noticed some confusion in our development community on when to use
> the Reported-by: tag. Some of this apparently is caused by the
> inconsistency fixed in this patch. Ciao, Thorsten
> ---
>  Documentation/process/5.Posting.rst | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)

Applied, thanks.

jon