linux-kernel - Re: [PATCH] MAINTAINERS: use relevant mailing lists

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070726173140.a76ff4a6.akpm@linux-foundation.org>
Date:	Thu, 26 Jul 2007 17:31:40 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: use relevant mailing lists

On Thu, 26 Jul 2007 17:08:57 -0700 Randy Dunlap <randy.dunlap@...cle.com> wrote:

> +	Use the relevant mailing list(s) -- don't just send everything to
> +	lkml (linux-kernel@...r.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.

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/