From: Sean Christopherson <seanjc@google.com>
To: Roman Gushchin <kfree@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sashiko-bot@kernel.org's Cc list on reviews
Date: Mon, 18 May 2026 16:27:47 -0700 [thread overview]
Message-ID: <agugc_uo58qXHN98@google.com> (raw)
In-Reply-To: <aguSFIoEbE_PPpeB@google.com>
On Mon, May 18, 2026, Sean Christopherson wrote:
> On Mon, May 18, 2026, Roman Gushchin wrote:
> > On Mon, May 18, 2026 at 2:08 PM Sean Christopherson <seanjc@google.com> wrote:
> > >
> > > Hey Roman!
> > >
> > > Sashiko's choice of Cc is... odd. The original mail has a whole pile of folks
> > > in both the To: and Cc:, but sashiko-bot is only replying to myself and (very
> > > bizarrely) linux-hyperv@vger.kernel.org.
> > >
> > > Oooh, is it perhaps because linux-hyperv@vger.kernel.org is the only mailing
> > > list on the original Cc that has opted-in to getting emails? If that's the case,
> > > we might want to change that, even though it could result in people getting grumpy
> > > about unwanted bot mail, because IMO the alternative is worse. I've been responding
> > > to some (mostly very good!) good sashiko-bot feedback, but only just now noticed
> > > that the vast majority of folks on the To/Cc of the original patch won't see the
> > > reviews. That's bound to cause confusion, e.g. if someone reports the same issues
> > > and/or manually looks at sashiko.dev.
> >
> > Hi Sean!
> >
> > It's expected per configuration here:
> > https://github.com/sashiko-dev/sashiko/blob/main/sashiko.dev/email_policy.toml#L138
> > .
> > It can be configured to reply to all as well, but since there are some
> > very vocal anti-AI folks in the community, this might create some
> > friction.
>
> Heh, "might".
>
> > In any case, I'm relying on the corresponding maintainers' decision on how
> > they want to configure Sashiko.
>
> What level of configurability does the parser have? Specifically, can it key off
> the Cc/To in addition to the list? I ask because I really, really, want to enable
> auto-mailing for at least KVM x86, but kvm@vger.kernel.org is wildly overloaded.
> I could try and drive consensus across all 30+ maintainers, but if there's a way
> to precisely enable it for just KVM x86...
>
> E.g. is there a way to do something like:
>
> [subsystems.kvm_x86]
> lists = ["kvm@vger.kernel.org" && <email is To: seanjc@google.com>]
> reply_all = true
Actually, shouldn't this be a line item in MAINTAINERS? E.g. an "A:" section
to describe the subsystem's preferences for AI reviews (and in the future, other
things?).
next prev parent reply other threads:[~2026-05-18 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 21:08 sashiko-bot@kernel.org's Cc list on reviews Sean Christopherson
2026-05-18 21:39 ` Roman Gushchin
2026-05-18 22:26 ` Sean Christopherson
2026-05-18 23:27 ` Roman Gushchin
2026-05-18 23:59 ` Sean Christopherson
2026-05-18 23:27 ` Sean Christopherson [this message]
2026-05-18 23:35 ` 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=agugc_uo58qXHN98@google.com \
--to=seanjc@google.com \
--cc=kfree@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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.