From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: use relevant mailing lists
Date: Fri, 27 Jul 2007 10:53:43 -0700 [thread overview]
Message-ID: <20070727105343.6486c74a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070726173140.a76ff4a6.akpm@linux-foundation.org>
On Thu, 26 Jul 2007 17:31:40 -0700 Andrew Morton wrote:
> On Thu, 26 Jul 2007 17:08:57 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > + Use the relevant mailing list(s) -- don't just send everything to
> > + lkml (linux-kernel@vger.kernel.org).
>
> True.
>
> I personally only troll lkml for unloved patches, so I suspect that a
> random patch which is sent to mailing-list-A and not to lkml has a higher
> probability of getting lost than one which is sent to both lists. Plus
> it'd be nice to get lkml's patch-to-noise ratio above one percent.
Yes (to P-N ratio).
I'd really like to see netdev patches going to netdev (only :)
and SCSI patches to linux-scsi (only), e.g., unless they actually
address some linux-arch like issue(s).
However, those maintainers are quite different regarding patch
handling. Maybe you could try to address some of that at that
Cambridge/September event.
> So I'd suggest that you rework the text here to make it clearer that
> patches should go to lkml _and_ to the subsystem-specific mailing list.
Patch is withdrawn.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-07-27 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 0:08 [PATCH] MAINTAINERS: use relevant mailing lists Randy Dunlap
2007-07-27 0:17 ` Jesper Juhl
2007-07-27 0:31 ` Randy Dunlap
2007-07-27 0:31 ` Andrew Morton
2007-07-27 17:53 ` Randy Dunlap [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=20070727105343.6486c74a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--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