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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 23 May 2009 22:51:24 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Joe Perches <joe@...ches.com>
Cc:	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:39 PM, Joe Perches <joe@...ches.com> wrote:
> On Sat, 2009-05-23 at 22:28 -0600, Grant Likely wrote:
>> On Sat, May 23, 2009 at 9:22 PM, Joe Perches <joe@...ches.com> wrote:
>> > On Sat, 2009-05-23 at 21:18 -0600, Grant Likely wrote:
>> >> Really?  That makes the assumption that lack of an "L:" tag is
>> >> equivalent to an "L:linux-kernel" tag, which IMNSHO I don't believe is
>> >> true.
>> > Documentation/SubmittingPatches
>> > 6) Select your CC (e-mail carbon copy) list.
>> > 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.
>
> Hi Grant.
>
> I think cc:ing lkml should be the default for patches.

Do subsystem maintainers think so?  Unless they do (and tell others
so), I don't think it will actually happen.  Until that point, I don't
think the L:linux-kernel lines should be removed.

> Having a few selected sections have lkml entries
> might make people think that a section that doesn't
> specifically mention lkml therefore wouldn't need to
> a cc: to lkml.
>
> Perhaps MAINTAINERS should mention that its preface
> as well as having it in Documentation/SubmittingPatches?

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/