From: Peter Zijlstra <peterz@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] get_maintainer: Add --prefix option
Date: Wed, 26 Jun 2019 19:18:13 +0200 [thread overview]
Message-ID: <20190626171813.GO3419@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <b007126ee329ba5094d84f0af91c0c8eafecbed4.camel@perches.com>
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.
prev parent reply other threads:[~2019-06-26 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 13:03 [PATCH] get_maintainer: Add --cc option Sebastian Andrzej Siewior
2019-06-24 13:33 ` Peter Zijlstra
2019-06-24 14:27 ` Joe Perches
2019-06-24 20:25 ` Peter Zijlstra
2019-06-24 20:42 ` Joe Perches
2019-06-25 7:45 ` Peter Zijlstra
2019-06-28 9:25 ` [PATCH] get_maintainer: Add ability to skip moderated mailing lists Joe Perches
2019-06-25 16:37 ` [PATCH v2] get_maintainer: Add --prefix option Sebastian Andrzej Siewior
2019-06-25 17:23 ` Joe Perches
2019-06-26 9:36 ` Peter Zijlstra
2019-06-26 15:36 ` Joe Perches
2019-06-26 17:18 ` Peter Zijlstra [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=20190626171813.GO3419@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=joe@perches.com \
--cc=linux-kernel@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
Powered by JetHome