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:	Tue, 26 May 2009 22:38:38 -0700
From:	Joe Perches <joe@...ches.com>
To:	Paul Mundt <lethal@...ux-sh.org>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	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 Wed, 2009-05-27 at 10:33 +0900, Paul Mundt wrote:
> On Sat, May 23, 2009 at 10:51:24PM -0600, Grant Likely wrote:
> > 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.
> > 
> Ultimately it should come to common sense. If you are only touching
> subsystem or architecture-specific code and it's unlikely anyone on l-k
> is going to care, or have much to add to it, then there really isn't a
> lot of point in mindlessly Cc-ing the list on every change.

And if you already know who or to what list you
want to submit a patch to, the MAINTAINERS entry
doesn't much matter.

> Conversely, if you need to read SubmittingPatches to figure out how to
> submit a patch, yes, you are probably better off CCing l-k just to be on
> the safe side. As a blanket policy though it makes no sense.

Yup.  Agree.

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