All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	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: Mon, 17 Mar 2025 16:49:09 -0600	[thread overview]
Message-ID: <878qp3e0ii.fsf@trenco.lwn.net> (raw)
In-Reply-To: <87jz8tlvqa.fsf@trenco.lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Sorry for being slow ... but also, I guess, for not communicating my
> point very well.  My concern wasn't about somebody not wanting to appear
> in the repository at all; it was more with somebody not wanting their
> tag in a specific patch where they had not offered it.
>
> It seems I'm the only one who is worried about this, though.  It seems
> like we should go ahead and get this change in before the merge window
> hits.

OK, I have gone ahead and applied it ... though I'm still not 100%
comfortable with the wording as it is... :)

Thanks,

jon

      reply	other threads:[~2025-03-17 22:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 14:30 [PATCH v4] docs: clarify rules wrt tagging other people 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
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 [this message]

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=878qp3e0ii.fsf@trenco.lwn.net \
    --to=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=linux@leemhuis.info \
    --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 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.