From: Richard Weinberger <richard@nod.at>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ian.Campbell@citrix.com, florian@mickler.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_maintainer.pl: Add support for moderated lists
Date: Fri, 02 Mar 2012 16:02:35 +0100 [thread overview]
Message-ID: <4F50E10B.6040806@nod.at> (raw)
In-Reply-To: <1330564646.23314.23.camel@joe2Laptop>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Am 01.03.2012 02:17, schrieb Joe Perches:
> On Wed, 2012-02-29 at 16:02 -0800, Andrew Morton wrote:
>> On Wed, 29 Feb 2012 21:06:45 +0100
>> Richard Weinberger <richard@nod.at> wrote:
>>
>>> Am 29.02.2012 20:58, schrieb Joe Perches:
>>>> <shrug> From my perspective, it's correct and simple.
>>>>
>>>> Moderated lists just means your email may get delayed
>>>> and you may get a "delayed due to moderation" email.
>>>
>>> Most moderated lists are "moderated" by nobody and the patch
>>> goes to /dev/null.
>>
>> That's a big problem - we don't want people to send their fixes and bug
>> reports into black holes.
>>
>> So yes, I think that teaching get_maintainer to emit black hole
>> warnings is a good idea.
>>
>> Problem is, I don't think the string "moderated" explains the situation
>> very well for the uninitiated :(
>
> It's also false. Most moderated lists in MAINTAINERS
> (and I've probably send patches to most of them) are
> in fact moderated.
What about linux@lists.openrisc.net?
None of my patches shows up there:
http://lists.openrisc.net/pipermail/openrisc/
> My patches generally show up in their list archives.
>
You must be a lucky guy. ;-)
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-03-02 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 19:49 [PATCH] get_maintainer.pl: Add support for moderated lists Richard Weinberger
2012-02-29 19:58 ` Joe Perches
2012-02-29 20:06 ` Richard Weinberger
2012-02-29 20:16 ` Joe Perches
2012-03-01 0:02 ` Andrew Morton
2012-03-01 0:27 ` Richard Weinberger
2012-03-01 1:17 ` Joe Perches
2012-03-02 15:02 ` Richard Weinberger [this message]
2012-03-02 21:18 ` Jonas Bonn
2012-03-02 17:13 ` Joe Perches
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=4F50E10B.6040806@nod.at \
--to=richard@nod.at \
--cc=Ian.Campbell@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=florian@mickler.org \
--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