From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: encourage direct notifications to reviewers
Date: Mon, 2 Oct 2023 19:04:15 +0200 [thread overview]
Message-ID: <4dd558eb-516d-4a92-8c6b-273877eb6751@t-8ch.de> (raw)
In-Reply-To: <ZRqEQ2uxAlCyihS3@infradead.org>
On 2023-10-02 01:50:11-0700, Christoph Hellwig wrote:
> On Mon, Oct 02, 2023 at 10:36:01AM +0300, Jani Nikula wrote:
> > On Sun, 01 Oct 2023, Christoph Hellwig <hch@infradead.org> wrote:
> > > On Fri, Sep 29, 2023 at 09:24:57AM +0200, Thomas Weißschuh wrote:
> > >> > This does not scale.
> > >>
> > >> Could you elaborate in which way it doesn't scale?
> > >
> > > If I send a modest cross-subsystem series it often touches 20+
> > > subsystems. Between mailing lists and maintainers that's usually
> > > already 60+ recipients. If you now add a another 2-3 maintainers
> > > we're just going to hit limits in mail servers.
> >
> > I thought this was about adding people who have commented on previous
> > versions to Cc. That's usually a very limited number.
>
> Oh, that absolutely makes sense. But maybe we need to stop overloading
> the term reviewer :)
Thanks Jani for fixing the misunderstanding!
I'll try to find some better wording.
prev parent reply other threads:[~2023-10-02 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:52 [PATCH] docs: submitting-patches: encourage direct notifications to reviewers Thomas Weißschuh
2023-09-28 9:13 ` Christoph Hellwig
2023-09-28 9:17 ` Laurent Pinchart
2023-09-29 7:24 ` Thomas Weißschuh
2023-10-02 6:34 ` Christoph Hellwig
2023-10-02 7:36 ` Jani Nikula
2023-10-02 8:50 ` Christoph Hellwig
2023-10-02 17:04 ` Thomas Weißschuh [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=4dd558eb-516d-4a92-8c6b-273877eb6751@t-8ch.de \
--to=linux@weissschuh.net \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).