linux-kernel - Re: [PATCH 16/18] MAINTAINERS - Remove L: linux-kernel@...r.kernel.org from all but "THE REST"

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 24 May 2009 11:42:01 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Joe Perches <joe@...ches.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 16/18] MAINTAINERS - Remove L:
	linux-kernel@...r.kernel.org from all but "THE REST"

On Sat, May 23, 2009 at 10:28:19PM -0600, Grant Likely wrote:
> On Sat, May 23, 2009 at 9:22 PM, Joe Perches <joe@...ches.com> wrote:

> > Unless you have a reason NOT to do so, CC linux-kernel@...r.kernel.org.

> Is that actually true in practice?  At least on linuxppc-dev, very few
> patches are cc'd to lkml.  I don't remember ever being prompted to cc
> lkml on all patches, and I haven't been prompting others to do so.

I regularly have to remind people to CC lkml as well as the architecture
list for the platform they're making changes to kernel wide subsystems
(partcularly the regulator framework).
--
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/