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]

Message-ID: <20190626171813.GO3419@hirez.programming.kicks-ass.net>
Date:   Wed, 26 Jun 2019 19:18:13 +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 Wed, Jun 26, 2019 at 08:36:33AM -0700, Joe Perches wrote:
> On Wed, 2019-06-26 at 11:36 +0200, Peter Zijlstra wrote:

> If a moderator of a list decides an email chain about a
> patch is somehow off-topic and does not forward the email,
> likely that moderated list should be removed from MAINTAINERS.

I think I've seen kernel-hardening complain about this; and that's not
even a moderated list I think. Yes, the patch touched one of 'their'
files, but was mostly unrelated.

I forgot the exact thread.

> Under what use case would you want to use get_maintainer and
> _not_ cc a particular mailing list?

I'm basically going to never send anything to a moderated list, ever.
It's what I've been doing for a long while, but I got lazy the other day
because a patch I did was a wide spray all over the tree and I didn't
want to manually compose the Cc list.