From: Jakub Kicinski <kuba@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>, Theodore Tso <tytso@mit.edu>,
"Darrick J. Wong" <djwong@kernel.org>,
Joanne Koong <joannelkoong@gmail.com>,
changfengnan@bytedance.com,
Christian Brauner <brauner@kernel.org>,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: selective Sashiko replies, was: Re: [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw
Date: Tue, 28 Jul 2026 07:27:56 -0700 [thread overview]
Message-ID: <20260728072756.7ddc9fdd@kernel.org> (raw)
In-Reply-To: <20260728040120.GA19400@lst.de>
On Tue, 28 Jul 2026 06:01:20 +0200 Christoph Hellwig wrote:
> > 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.
+1, maybe perhaps someone wants the off-list option, dunno.
But trimming the CC list of the on-list reply is a really weird idea.
Submissions often CC multiple vger lists, and the bot only replies to one.
next prev parent reply other threads:[~2026-07-28 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260722124931.3159664-1-hch@lst.de>
[not found] ` <20260722124931.3159664-3-hch@lst.de>
[not found] ` <CAJnrk1a_cc55HcpRAi+H-mqOn7XUt_BxKJTre=Mw=xaE-5A5Rg@mail.gmail.com>
[not found] ` <20260723045347.GA6641@lst.de>
[not found] ` <20260723151021.GC7380@frogsfrogsfrogs>
[not found] ` <amI3Kf3lFz4FMqXh@mit.edu>
[not found] ` <amNerp4LwjSkHS5t@andromeda.toxiclabs.cc>
2026-07-28 4:01 ` selective Sashiko replies, was: Re: [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw Christoph Hellwig
2026-07-28 14:27 ` Jakub Kicinski [this message]
2026-07-28 14:42 ` Theodore Tso
2026-07-28 17:28 ` Jonathan Corbet
2026-07-28 17:46 ` Jakub Kicinski
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=20260728072756.7ddc9fdd@kernel.org \
--to=kuba@kernel.org \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=changfengnan@bytedance.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=joannelkoong@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox