public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: Joe Perches <joe@perches.com>,
	Ian.Campbell@citrix.com, florian@mickler.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_maintainer.pl: Add support for moderated lists
Date: Wed, 29 Feb 2012 16:02:54 -0800	[thread overview]
Message-ID: <20120229160254.eda62e01.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F4E8555.5040002@nod.at>

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 :(


  parent reply	other threads:[~2012-03-01  0:03 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 [this message]
2012-03-01  0:27       ` Richard Weinberger
2012-03-01  1:17       ` Joe Perches
2012-03-02 15:02         ` Richard Weinberger
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=20120229160254.eda62e01.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=florian@mickler.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    /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