mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [GIT PULL] Performance events updates for v7.3
Date: Sun, 23 Aug 2026 12:22:57 +0200	[thread overview]
Message-ID: <aorKASsneqj-jpwC@gmail.com> (raw)
In-Reply-To: <CAHk-=whfHkbCuZ1bZp2+0-+6KjsQxmyJ79StB-a0rO+cZN+3oA@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, 17 Aug 2026 at 02:30, Ingo Molnar <mingo@kernel.org> wrote:
> >
> >  - Patch series to fix a category of bugs [..]
> ...
> >  - Series to fix various uncore [..]
>
> In today's small pet peeve, you seem to have caught the same pointless
> verbiage bug that I've been editing out of other peoples'
> explanations: I really don't think it adds any value to talk about how
> one issue was fixed by X patches, and another was fixed by a single
> patch.
>
> Just say "Fix a category of bugs ..." and "Fix various uncore ..". The
> important thing is what got fixed, not that it was a "Five-patch
> series fixing XYZ" like some people seem to think.
>
> No, this isn't a big deal. I edit other peoples messages a lot more.
> Some people seem to not understand imperative mood, and keep doing
> that "Series fixing XYZ" thing.
>
> The only reason I mention it is that I don't think I _used_ to do it
> for your messages.

Yeah, so this was indeed a recent change of mine, I got the brilliant
idea to improve the pull request verbiage from the somewhat ambiguous
and perhaps a bit dismissive 'various' wording of larger changes to the
'series' phrasing, which intended to give the (significantly) higher
underlying effort a bit more credit while keeping the description
more compressed (and I tried to only apply it where it was justified,
so a simple cleanup series does not necessarily earn the same weight),
but looks like it's a regression and annoyance, so I reverted the
brain patch ;-)

I'll simply bring back more verbose summaries in those cases, or
use the 'various' verbiage.

Thanks,

	Ingo

  reply	other threads:[~2026-08-23 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  9:30 Ingo Molnar
2026-08-18 19:42 ` Linus Torvalds
2026-08-23 10:22   ` Ingo Molnar [this message]
2026-08-18 22:00 ` pr-tracker-bot

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=aorKASsneqj-jpwC@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®