All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: SJ Park <sj@kernel.org>, Matthieu Baerts <matttbe@kernel.org>,
	Alexey Gladkov <legion@kernel.org>,
	oleg@kernel.org, sashiko@lists.linux.dev, users@linux.kernel.org
Subject: Re: direct replies from sashiko
Date: Sat,  3 Oct 2026 10:10:44 -0700	[thread overview]
Message-ID: <20261003171045.33520-1-sj@kernel.org> (raw)
In-Reply-To: <7ia4pkxt5ob6.fsf@castle.c.googlers.com>

Hello Roman and Sashiko team,

On Thu, 01 Oct 2026 17:21:49 +0000 Roman Gushchin <roman.gushchin@linux.dev> wrote:

> Matthieu Baerts <matttbe@kernel.org> writes:
> Hey!
> 
> Several questions here:
> 1) What mailing list are we talking about? There are per-mailing list
> policies defining if and who sashiko is sending emails.
> 2) Do you see findings in corresponding patches on sashiko.dev?
> Sashiko previously reported preexisting bugs together with new bugs,
> but now it's putting them into the database available to corresponding
> maintainers ("bugs" button on sashiko.dev), so the number of emails
> might naturally drop.
> 3) There might be a bug somewhere :) I need more details to dig in.

I also noticed Sashiko is not sending reviews as replies to patches that are
sent to damon@lists.linux.dev.

The last time I got the review reply [1] was 2026-10-02 07:14 (PT).
Today I sent a patch [2] and didn't receive the review as a reply to the patch.

Also, from Sashiko web interface's subsystems dropdown menu, I show two menu
entries [3,4] for 'damon'.  Given the URL, it seems the second one [4] is based
on a wrong DAMON mailing list address.

Could you please take a look when you get a chance?

[1] https://lore.kernel.org/20261002141421.AF3431F000FF@smtp.kernel.org
[2] https://lore.kernel.org/20261003163101.32739-1-sj@kernel.org
[3] https://sashiko.dev/#/?list=dev.linux.lists.damon
[4] https://sashiko.dev/#/?list=org.kernel.vger.damon


Thanks,
SJ

[...]

  parent reply	other threads:[~2026-10-03 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ar47HvytXrbOiwTO@example.org>
2026-10-01 14:56 ` direct replies from sashiko Matthieu Baerts
2026-10-01 17:21   ` Roman Gushchin
2026-10-02  9:50     ` Alexey Gladkov
2026-10-03 17:10     ` SJ Park [this message]
2026-10-03 18:07       ` SJ Park
2026-10-03 20:15       ` Roman Gushchin
2026-10-02  9:41   ` Alexey Gladkov
2026-10-02 10:29     ` Oleg Nesterov
2026-10-03 19:09       ` Roman Gushchin

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=20261003171045.33520-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=legion@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=oleg@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=sashiko@lists.linux.dev \
    --cc=users@linux.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.