linux-kernel - Re: [PATCH v2] get_maintainer: Add --prefix option

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 26 Jun 2019 11:36:35 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Joe Perches <joe@...ches.com>
Cc:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] get_maintainer: Add --prefix option

On Tue, Jun 25, 2019 at 10:23:34AM -0700, Joe Perches wrote:
> There are now simple ways to make sure a patch
> submission is cc'd to appropriate parties.
> 
> git send-email supports --cc-cmd

That assumes one is using git; I'm not, git stinks.

> I want to proposed patches to moderated lists
> and believe everyone really should too.
> 
> I don't care if moderated lists send a
> "waiting for moderation" message as long as the
> list gets the proposed patch eventually.
> 
> I think only Peter cares about those, to him,
> superfluous "being moderated" messages.

I'm really not alone in that. Not only do you get those annoying
messages, the people reading that list might get the discussion in
fragments, because some people that reply are subscribed and do not
require moderation while others do get caught in the moderation thing
and then delayed.

It also puts a burden on the moderator, do they allow the whole
discussion or only part. What if they deem the thing off-topic and want
to kill it, but then some of their whitelisted people do reply.

Cross-posting to moderated lists has been considered bad form ever since
I got on the interweb in the early 90s.