linux-kernel - Re: [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@...r.kernel.org

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]

Date:	Wed, 08 Jul 2009 09:55:02 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@...r.kernel.org

Hi Joe,

On Tue, 2009-07-07 at 23:39 -0700, Joe Perches wrote:
> > > Documentation/SubmittingPatches already states that
> > > LKML should be CC'd on all patches.

On Wed, 2009-07-08 at 09:44 +0300, Pekka Enberg wrote:
> > Maybe it does, but real world doesn't seem to agree with you here.

On Tue, 2009-07-07 at 23:47 -0700, Joe Perches wrote:
> Well, if scripts/get_maintainer.pl gets used more often,
> it would.

And kernel hackers could fly if they had wings.

Look, all I care is that people who send patches to subsystems I
maintain know what to CC. The get_maintainer.pl script is obviously
really helpful here but the fact is, it's _not_ mandatory to CC LKML for
all patches. So I worry that people will be confused and no list is CC'd
because other subsystems that have a separate mailing list have that in
MAINTAINERS.

But anyway, no need to argue about this, Andrew merged your first patch
so the second patch makes sense as well.

			Pekka

--
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/