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 11:36:35 +0200 [thread overview]
Message-ID: <20190626093635.GK3419@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <8d416a7b0dad3933ceb8d12c9efaad541f7cf269.camel@perches.com>
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.
next prev parent reply other threads:[~2019-06-26 9:36 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 [this message]
2019-06-26 15:36 ` Joe Perches
2019-06-26 17:18 ` Peter Zijlstra
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=20190626093635.GK3419@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