From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@vger.kernel.org
Date: Wed, 08 Jul 2009 09:55:02 +0300 [thread overview]
Message-ID: <1247036102.15919.41.camel@penberg-laptop> (raw)
In-Reply-To: <1247035628.5124.11.camel@Joe-Laptop.home>
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
next prev parent reply other threads:[~2009-07-08 6:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 5:55 [PATCH 0/7] MAINTAINERS: cleanups Joe Perches
2009-07-08 5:55 ` [PATCH 1/7] MAINTAINERS: IA64 - pair P:/M: entries properly Joe Perches
2009-07-08 5:55 ` [PATCH 2/7] MAINTAINERS: Remove ivtv-user lists, add CX18 url Joe Perches
2009-07-08 5:55 ` [PATCH 3/7] MAINTAINERS: QLGE 10Gb ETHERNET - pair P:/M: entries properly Joe Perches
2009-07-08 5:55 ` [PATCH 4/7] MAINTAINERS: Use tabs in ACER ASPIRE ONE Joe Perches
2009-07-08 5:55 ` [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@vger.kernel.org Joe Perches
2009-07-08 6:32 ` Pekka Enberg
2009-07-08 6:39 ` Joe Perches
2009-07-08 6:44 ` Pekka Enberg
2009-07-08 6:47 ` Joe Perches
2009-07-08 6:55 ` Pekka Enberg [this message]
2009-07-08 16:37 ` Maciej W. Rozycki
2009-07-09 9:30 ` Mark Brown
2009-07-09 14:58 ` Joe Perches
2009-07-09 15:08 ` Mark Brown
2009-07-09 19:35 ` Joe Perches
2009-07-10 13:17 ` Mark Brown
2009-07-10 16:25 ` Joe Perches
2009-07-10 18:44 ` Mark Brown
2009-07-10 19:16 ` Joe Perches
2009-07-08 5:55 ` [PATCH 6/7] MAINTAINERS: Move ARPD to CREDITS Joe Perches
2009-07-08 5:55 ` [PATCH 7/7] MAINTAINERS: Update KERNEL JANITORS Joe Perches
2009-07-09 2:25 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1247036102.15919.41.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®