From: Eric Biggers <ebiggers@kernel.org>
To: Thomas Huth <thuth@redhat.com>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Ard Biesheuvel <ardb@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: Enabling Sashiko replies to linux-crypto?
Date: Tue, 20 Oct 2026 23:54:59 -0700 [thread overview]
Message-ID: <20261021065459.GD31908@sol> (raw)
In-Reply-To: <d3dc7e74-0189-4aa6-b23d-0fa8ad75e059@redhat.com>
On Wed, Oct 21, 2026 at 08:18:18AM +0200, Thomas Huth wrote:
> On 20/10/2026 23.57, Eric Biggers wrote:
> > Currently, Sashiko is configured (in
> > https://github.com/sashiko-dev/sashiko/blob/main/projects/linux/mailing_lists.toml)
> > to monitor linux-crypto for patches, but not to send emails to it.
> >
> > Would there be any objections to me opening a pull request that changes
> > it to the same setting that I set the fscrypt and fsverity lists to?
> >
> > ["linux-crypto@vger.kernel.org"]
> > reply_to = ["author", "list", "recipients"]
> >
> > That would enable emails for issues found, with reply-all.
> >
> > (There's also a 'positive_review = "all"' setting that would enable
> > emails for positive reviews, i.e. "Sashiko has reviewed this patch and
> > found no issues. It looks great!" But those are kind of noisy.)
> Is it possible to configure it in a way that it only sends mails if it
> really found something? ... always getting "Sashiko has reviewed this patch
> and it looks great" mails is rather annoying than helpful ...
Yes, that's what I proposed above (and it's merged now).
- Eric
next prev parent reply other threads:[~2026-10-21 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 21:57 Enabling Sashiko replies to linux-crypto? Eric Biggers
2026-10-20 22:12 ` Jason A. Donenfeld
2026-10-21 2:53 ` Herbert Xu
2026-10-21 6:18 ` Thomas Huth
2026-10-21 6:54 ` Eric Biggers [this message]
2026-10-21 7:25 ` Thomas Huth
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=20261021065459.GD31908@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=thuth@redhat.com \
/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.