From: Benjamin Marzinski <bmarzins@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: dm-devel@lists.linux.dev, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: Enabling Sashiko for dm-devel?
Date: Thu, 22 Oct 2026 12:36:59 -0400 [thread overview]
Message-ID: <ato7qykzvctpGmdy@redhat.com> (raw)
In-Reply-To: <atkdtNT83DBoCTVS@redhat.com>
On Wed, Oct 21, 2026 at 04:16:52PM -0400, Benjamin Marzinski wrote:
> On Wed, Oct 21, 2026 at 10:39:43AM -0700, Eric Biggers wrote:
> > Currently, Sashiko doesn't monitor dm-devel or send email replies to it
> > (https://github.com/sashiko-dev/sashiko/blob/main/projects/linux/mailing_lists.toml).
> >
> > Sometimes Sashiko reviews for device-mapper patches can be found on
> > https://sashiko.dev anyway, due to the patches also being Cc'ed to
> > linux-kernel which is monitored. However, get_maintainer.pl is being
> > updated to no longer suggest Cc'ing linux-kernel.
> >
> > Would there be any objection to enabling monitoring and email replies
> > for dm-devel, like this which various other lists already use?:
> >
> > ["dm-devel@lists.linux.dev"]
> > reply_to = ["author", "list", "recipients"]
> >
> > If the dm maintainers prefer monitoring-only (no emails), that could be
> > done instead. But I think the email replies are really helpful.
>
> Sounds good, and I think emailing when issues are found is fine. I'll go
> open a Pull Request to add this.
This has been added:
https://github.com/sashiko-dev/sashiko/pull/724
>
> Thanks
> -Ben
>
> >
> > - Eric
>
prev parent reply other threads:[~2026-10-22 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 17:39 Enabling Sashiko for dm-devel? Eric Biggers
2026-10-21 20:16 ` Benjamin Marzinski
2026-10-22 16:36 ` Benjamin Marzinski [this message]
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=ato7qykzvctpGmdy@redhat.com \
--to=bmarzins@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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