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: <1298980419.4367.18.camel@Joe-Laptop>
Date:	Tue, 01 Mar 2011 03:53:39 -0800
From:	Joe Perches <joe@...ches.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/18] MAINTAINERS: Remove unnecessary
 linux-kernel@...r.kernel.org entries

On Tue, 2011-03-01 at 11:20 +0000, Mark Brown wrote:
> On Tue, Feb 22, 2011 at 09:41:58PM -0800, Joe Perches wrote:
> > CC'ing lkml is the default and doesn't need separate entries.
> I've run into a noticeable number of issues with users not parsing this
> convention as expected and sending only direct to maintainer mail for
> things that have no list.  For the amount of space it saves in the file
> I'm not sure it's worth removing such entries.

Yes that's certainly possible, but it's a trade-off given the
number of people that would not otherwise CC lkml after seeing
some MAINTAINERS entries with
L: linux-kernel@...r...
and some entries without.

It might also be worthwhile to to update
Documentation/SubmittingPatches.

Currently, it says to do what you find inappropriate,
direct mails to listed maintainers without cc'ing a list.

It also does not mention scripts/get_maintainer.pl.

-------------------------------------------------------------

5) Select e-mail destination.

Look through the MAINTAINERS file and the source code, and determine
if your change applies to a specific subsystem of the kernel, with
an assigned maintainer.  If so, e-mail that person.

If no maintainer is listed, or the maintainer does not respond, send
your patch to the primary Linux kernel developer's mailing list,
linux-kernel@...r.kernel.org.  Most kernel developers monitor this
e-mail list, and can comment on your changes.

-------------------------------------------------------------


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ