workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Neal Gompa <neal@gompa.dev>, Miguel Ojeda <ojeda@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	Sami Tolvanen <samitolvanen@google.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	tech-board@groups.linuxfoundation.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 3/3] docs: submitting-patches: clarify that signers may use their discretion on tags
Date: Mon, 13 Jan 2025 10:36:45 -0500	[thread overview]
Message-ID: <20250113103645.1f23b3b7@gandalf.local.home> (raw)
In-Reply-To: <20250113142227.GE1514771@mit.edu>

On Mon, 13 Jan 2025 09:22:27 -0500
"Theodore Ts'o" <tytso@mit.edu> wrote:

> On Sun, Jan 12, 2025 at 10:47:02AM -0500, Neal Gompa wrote:
> > 
> > A tag must not be dropped without the tag submitter's authorization.
> > Otherwise it doesn't matter what you write here, the submitter *will*
> > feel unwelcome.
> > 
> > It is rude and discouraging to do so without their acceptance of doing so.  
> 
> In some cases, if the reviewer hasn't taken the less than subtle hints
> that their reviews are unwelcome and are discouraging patch
> submitters, as far as I'm concerned, if they feel unwelcome, that is a
> *feature* and not a *bug*.
> 
> I'm not saying that is the case for you, but there are reviewers that
> add negative value in the ecosystem.  The assumption that all tag
> submitters are people that need to feel welcome might mostly true, but
> it is not always the case.  This is why it MUST ultimately be up to
> the maintainer.  I do not want the rules that force me to reward
> people that should be discouraged, not encouraged.

I try to add all tags that are meaningful, but a lot of times I already
pulled in the patch, and there's been several times tags came in after I
did a pull request to Linus! (for fixes patches). Once I do a pull request to
Linus, only Linus can have me change that commit (if there's an issue with
it).

For linux-next, I will add tags, even when Linus told me to avoid doing so.

That said, I have ignored several "Reviewed-by" tags when they appear
random. If you send a "Reviewed-by" without a single comment, and I don't
know you, it is meaningless to me, and I will not add it.

Now for people I don't know, if they came in and found an issue with a
patch which requires another revision, I will most definitely add their
Reviewed-by for the next version (if they send one), and will likely take
Reviewed-by tags from them in the future without comments (up to a point).

There's also been several cases that someone sent a Reviewed-by tag and
when I take a look at the patch I find an obvious bug. That will cause me
to ignore that reviewer in the future. Adding that tag comes with
responsibilities. As I mentioned in another thread, if I give a Reviewed-by
and a bug happens on that commit, I will spend time to help fix it.

-- Steve

  reply	other threads:[~2025-01-13 15:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12 15:29 [PATCH 0/3] Clarifications around Acked-by and "# Suffix" proposal Miguel Ojeda
2025-01-12 15:29 ` [PATCH 1/3] docs: submitting-patches: clarify Acked-by and introduce "# Suffix" Miguel Ojeda
2025-01-12 15:52   ` Neal Gompa
2025-01-12 17:24   ` Greg Kroah-Hartman
2025-01-13 11:52   ` Krzysztof Kozlowski
2025-01-12 15:29 ` [PATCH 2/3] docs: submitting-patches: clarify difference between Acked-by and Reviewed-by Miguel Ojeda
2025-01-12 15:50   ` Neal Gompa
2025-01-12 16:31     ` Miguel Ojeda
2025-01-12 16:35       ` Neal Gompa
2025-01-12 17:10         ` Miguel Ojeda
2025-01-12 19:59         ` Jonathan Corbet
2025-01-12 20:13           ` Neal Gompa
2025-01-13 14:13         ` Theodore Ts'o
2025-01-13 11:48     ` Krzysztof Kozlowski
2025-01-13 12:38     ` Jani Nikula
2025-01-13 15:15       ` Steven Rostedt
2025-01-14 23:13     ` Darrick J. Wong
2025-01-12 17:25   ` Greg Kroah-Hartman
2025-01-13 11:50   ` Krzysztof Kozlowski
2025-01-12 15:29 ` [PATCH 3/3] docs: submitting-patches: clarify that signers may use their discretion on tags Miguel Ojeda
2025-01-12 15:47   ` Neal Gompa
2025-01-12 16:33     ` Miguel Ojeda
2025-01-12 17:24     ` Greg Kroah-Hartman
2025-01-13 13:36     ` Mark Brown
2025-01-13 14:22     ` Theodore Ts'o
2025-01-13 15:36       ` Steven Rostedt [this message]
2025-01-12 17:22   ` Greg Kroah-Hartman
2025-01-13 11:51   ` Krzysztof Kozlowski
2025-01-13 17:47 ` [PATCH 0/3] Clarifications around Acked-by and "# Suffix" proposal 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=20250113103645.1f23b3b7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=neal@gompa.dev \
    --cc=ojeda@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=samitolvanen@google.com \
    --cc=skhan@linuxfoundation.org \
    --cc=tech-board@groups.linuxfoundation.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --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