* selective Sashiko replies, was: Re: [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw
[not found] ` <amNerp4LwjSkHS5t@andromeda.toxiclabs.cc>
@ 2026-07-28 4:01 ` Christoph Hellwig
0 siblings, 0 replies; only message in thread
From: Christoph Hellwig @ 2026-07-28 4:01 UTC (permalink / raw)
To: Carlos Maiolino
Cc: Theodore Tso, Darrick J. Wong, Christoph Hellwig, Joanne Koong,
changfengnan, Christian Brauner, linux-ext4, linux-xfs,
linux-fsdevel, workflows
On Fri, Jul 24, 2026 at 02:47:58PM +0200, Carlos Maiolino wrote:
> > Whether or not the review goes to a mailing list is up to each
> > subsystem to determine. Some people have violently objected to the
> > review going to the mailing list, which is why it's optional.
> >
> > I have asked to have ext4 reviews to be cc'ed to the linux-ext4
> > list[1]. It would be up to the VFS maintainers whether or not we want
> > to enable it for linux-fsdevel.
> >
> > [1] https://github.com/sashiko-dev/sashiko/pull/365
> >
> > The XFS maintainers can request if patches cc'ed to linux-fs should
> > get reviewed and sent back to authors and/or the maintainers and/or
> > the linux-fs mailing list. You can either ask the Sashiko devs to
> > edit the email_policy.toml file, or you can send a pull request yourself.
> >
>
> IIRC the discussion we had a while back was to keep the reviews emailed
> to authors only...
>
> Now I wonder how feasible would be to have a "linux-xfs-review" list to
> send sashiko reviews to, then people opt-in to it? Would it be overkill?
The main problem is that reducing the recipient list for replies is
incredibly stupid. You can do that for a private offlist conversion
on something sensitive, but not by default. If I get a reply, it needs
to go everywhere. I have to admit I find the sashiko replies a lot
less useful than the web interface, but the important bit is to be
consistent.
^ permalink raw reply [flat|nested] only message in thread