lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4dd558eb-516d-4a92-8c6b-273877eb6751@t-8ch.de>
Date:   Mon, 2 Oct 2023 19:04:15 +0200
From:   Thomas Weißschuh <linux@...ssschuh.net>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Jani Nikula <jani.nikula@...el.com>,
        Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: encourage direct notifications
 to reviewers

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@...radead.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ