workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Simona Vetter <simona.vetter@ffwll.ch>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4] docs: clarify rules wrt tagging other people
Date: Tue, 11 Feb 2025 09:43:03 +0100	[thread overview]
Message-ID: <51ad94dc-4534-4255-b9d4-383ddd95cb5e@leemhuis.info> (raw)
In-Reply-To: <20250210111501.GF2966@pendragon.ideasonboard.com>

On 10.02.25 12:15, Laurent Pinchart wrote:
> On Sat, Feb 08, 2025 at 04:36:47PM +0100, Thorsten Leemhuis wrote:
>> On 07.02.25 10:05, Laurent Pinchart wrote:
>>> On Thu, Feb 06, 2025 at 03:30:10PM +0100, Thorsten Leemhuis wrote:
>>> [...]
>>>> +Be careful in the addition of the aforementioned tags to your patches, as all
>>>> +except for Cc:, Reported-by:, and Suggested-by: need explicit permission of the
>>>> +person named. For those three implicit permission is sufficient if the person
>>>> +contributed to the Linux kernel using that name and email address according
>>>> +to the lore archives or the commit history -- and in case of Reported-by:
>>>> +and Suggested-by: did the reporting or suggestion in public. Note,
>>>> +bugzilla.kernel.org is a public place in this sense, but email addresses
>>>> +used there are private; so do not expose them in tags, unless the person
>>>> +used them in earlier contributions.
> [...]
>> But I'm not sure how to solve that. Would simply
>> dropping the "explicit" solve this? Or should I start the section like this:
> 
> Dropping "explicit" seems to be the simplest solution, but the next
> sentence mentions "implicit permission" which would then sound weird.

TBH: a bit, yes, but I think I'd prefer that a tiny bit over making that
section yet again a few lines longer. But I don't care much. Maybe
someone else (Jonathan?) can weight in on this?

>> ""
>> Be careful in the addition of the aforementioned tags to your patches,
>> almost all need permission by the person named; one can be assumed if
>> the person provided that tag in a reply or acknowledged its inclusion
> 
> "in a reply to a public list"

Yes, albeit I'd go with "public reply" (shorter, and does not exclude a
reply in a public bug tracker comment).

>> after being made aware that name and email address will end up in public
>> places where they can't be removed.
>>
>> The tags Cc:, Reported-by:, and Suggested-by: are an exception: for
>> those three implicit permission is sufficient, ...
>> """
> This sounds good to me.

Thx!

Ciao, Thorsten

  reply	other threads:[~2025-02-11  8:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 14:30 Thorsten Leemhuis
2025-02-07  1:42 ` Bagas Sanjaya
2025-02-07  8:24   ` Thorsten Leemhuis
2025-02-10 16:16     ` Mauro Carvalho Chehab
2025-02-11  8:45       ` Thorsten Leemhuis
2025-02-07  9:05 ` Laurent Pinchart
2025-02-08 15:36   ` Thorsten Leemhuis
2025-02-10 11:15     ` Laurent Pinchart
2025-02-11  8:43       ` Thorsten Leemhuis [this message]
2025-02-10 18:12 ` Jonathan Corbet
2025-02-11  8:48   ` Thorsten Leemhuis
2025-02-18 20:42     ` Jonathan Corbet
2025-03-06 13:31       ` Thorsten Leemhuis
2025-03-12 22:39         ` Jonathan Corbet
2025-03-17 22:49           ` Jonathan Corbet

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=51ad94dc-4534-4255-b9d4-383ddd95cb5e@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=simona.vetter@ffwll.ch \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    /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