Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jonathan Corbet <corbet@lwn.net>
To:     Thorsten Leemhuis <linux@leemhuis.info>
Cc:     linux-doc@vger.kernel.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] docs: process/5.Posting.rst: clarify use of
 Reported-by: tag
In-Reply-To: <2fc7162dfb76e04da5ea903c9c170d913e735dad.1664372256.git.linux@leemhuis.info>
References: <2fc7162dfb76e04da5ea903c9c170d913e735dad.1664372256.git.linux@leemhuis.info>
Date:   Thu, 29 Sep 2022 13:11:25 -0600
Message-ID: <87a66ihu76.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Thorsten Leemhuis <linux@leemhuis.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@leemhuis.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