From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: Summary of perf-tools-next changes and patches sent to linux-perf-users
Date: Mon, 25 May 2026 21:15:35 -0300 [thread overview]
Message-ID: <ahTmJyLLZYOPpnKa@x1> (raw)
In-Reply-To: <CAP-5=fX=vEmTaz6mWgExmrgyYMJmSyOD+1sMCzf7JTk1SkA-zQ@mail.gmail.com>
On Mon, May 25, 2026 at 04:35:51PM -0700, Ian Rogers wrote:
> Hi,
>
> I've been working on a script [1] to summarize what's been sent to the
> linux-perf-users mailing list (using nntp) and compare it to what's
> merged into the perf-tools-next branch (using git). The idea is to
> make it slightly easier to track down patches that might have been
> missed. The script shows what has been merged and what's pending, what
> Sashiko thinks, and whose turn it is to work on the patch (author,
> reviewer or maintainer) using some naive tag analysis. The output is
> quite large, so rather than adding it below, I will send the last 4
> weeks in separate e-mail replies to this message.
I'm doing this locally as well, helps.
- Arnaldo
next prev parent reply other threads:[~2026-05-26 0:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 23:35 Summary of perf-tools-next changes and patches sent to linux-perf-users Ian Rogers
2026-05-25 23:37 ` Ian Rogers
2026-05-25 23:38 ` Ian Rogers
2026-05-25 23:40 ` Ian Rogers
2026-05-25 23:41 ` Ian Rogers
2026-05-26 15:41 ` Arnaldo Carvalho de Melo
2026-05-26 16:20 ` Ian Rogers
2026-05-26 0:15 ` Arnaldo Carvalho de Melo [this message]
2026-05-26 0:21 ` Arnaldo Carvalho de Melo
2026-05-26 0:27 ` Arnaldo Carvalho de Melo
2026-05-26 3:25 ` Ian Rogers
2026-05-26 0:22 ` Namhyung Kim
2026-05-26 3:06 ` Ian Rogers
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=ahTmJyLLZYOPpnKa@x1 \
--to=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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