From: Paul Mundt <lethal@linux-sh.org>
To: Joe Perches <joe@perches.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 16/18] MAINTAINERS - Remove L: linux-kernel@vger.kernel.org from all but "THE REST"
Date: Wed, 27 May 2009 14:50:06 +0900 [thread overview]
Message-ID: <20090527055005.GA9802@linux-sh.org> (raw)
In-Reply-To: <1243402718.27337.8.camel@Joe-Laptop.home>
On Tue, May 26, 2009 at 10:38:38PM -0700, Joe Perches wrote:
> 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.
>
That's not true. If I have to hack something up in some random subsystem
then I will often have to hunt for both the list address (if there is one
at all!), as well as the folks looking after that code. Yes, I could
blindly send it to a given list, but it's much more likely to fall
through than sending it directly to the people who care.
MAINTAINERS is very useful for randomly looking up people and email
addresses, especially if they aren't people you routinely interact with.
It's also much faster to look through than remembering the proper
incantation for a specific perl script ;-)
Knowing where to look and knowing who to talk to are two different
things. Most subsystem maintainers only interact with a small group of
other subsystem maintainers on any sort of regular basis, while things
like build errors in -next often send you scurrying one way or the other.
next prev parent reply other threads:[~2009-05-27 5:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 2:37 [PATCH 00/18] MAINTAINERS and scripts/get_maintainer.pl updates Joe Perches
2009-05-24 2:37 ` [PATCH 01/18] scripts/get_maintainer.pl - Output first field only in mailing lists and after maintainers Joe Perches
2009-05-24 2:37 ` [PATCH 02/18] scripts/get_maintainer.pl - Better fix for subscriber-only mailing lists Joe Perches
2009-05-24 2:37 ` [PATCH 03/18] scripts/get_maintainer.pl - improve --git-chief-penquins (Linus Torvalds) filtering Joe Perches
2009-05-24 2:37 ` [PATCH 04/18] scripts/get_maintainer.pl - Warn on missing git or git repository Joe Perches
2009-05-24 2:37 ` [PATCH 05/18] scripts/get_maintainer.pl - support M: lines with names and multiple entries per M: line Joe Perches
2009-05-24 2:37 ` [PATCH 06/18] scripts/get_maintainer.pl - Better email name quoting Joe Perches
2009-05-24 2:37 ` [PATCH 07/18] scripts/get_maintainer.pl - Support both "P:/M:" and integrated "M:" lines Joe Perches
[not found] ` <20090526144141.570594cf.akpm@linux-foundation.org>
[not found] ` <1243455722.27337.65.camel@Joe-Laptop.home>
[not found] ` <20090527151510.fb773db6.akpm@linux-foundation.org>
2009-06-01 17:45 ` Script to integrate MAINTAINERS P: and M: lines Joe Perches
2009-06-02 9:12 ` Pavel Machek
2009-06-05 21:47 ` Sam Ravnborg
2009-06-05 22:57 ` Joe Perches
2009-05-24 2:37 ` [PATCH 08/18] scripts/get_maintainer.pl - Don't print maintainers when not requested Joe Perches
2009-05-24 2:37 ` [PATCH 09/18] scripts/get_maintainer.pl - Allow 8 bit characters in email addresses Joe Perches
2009-05-24 2:37 ` [PATCH 10/18] scripts/get_maintainer.pl - change "die" to "warn" when command line file is not a patch Joe Perches
2009-05-24 2:37 ` [PATCH 11/18] MAINTAINERS - Swap mismarked ECRYPT FS M: and P: entries Joe Perches
2009-05-24 2:37 ` [PATCH 12/18] MAINTAINERS - Pair EDAC-E752X P: and M: entries Joe Perches
2009-05-24 2:37 ` [PATCH 13/18] MAINTAINERS - Add file patterns to "THE REST" Joe Perches
2009-05-24 2:37 ` [PATCH 14/18] MAINTAINERS - Update M32R file patterns after rename Joe Perches
2009-05-24 2:37 ` [PATCH 15/18] MAINTAINERS - Mark ALSA lists as moderated Joe Perches
2009-05-24 2:37 ` [PATCH 16/18] MAINTAINERS - Remove L: linux-kernel@vger.kernel.org from all but "THE REST" Joe Perches
2009-05-24 3:18 ` Grant Likely
2009-05-24 3:22 ` Joe Perches
2009-05-24 4:28 ` Grant Likely
2009-05-24 4:39 ` Joe Perches
2009-05-24 4:51 ` Grant Likely
2009-05-24 4:58 ` Joe Perches
2009-05-27 1:33 ` Paul Mundt
2009-05-27 5:38 ` Joe Perches
2009-05-27 5:50 ` Paul Mundt [this message]
2009-05-27 6:00 ` Andrew Morton
2009-05-27 6:02 ` Paul Mundt
2009-05-27 16:12 ` Joe Perches
2009-05-24 10:42 ` Mark Brown
2009-05-26 23:42 ` Paul E. McKenney
2009-05-27 18:18 ` [PATCH] MAINTAINERS: Add Paul McKenney to RCU and RCUTORTURE Joe Perches
2009-05-27 21:03 ` Paul E. McKenney
2009-05-24 2:37 ` [PATCH 17/18] MAINTAINERS - Mention scripts/get_maintainer.pl in the preface Joe Perches
2009-05-24 2:37 ` [PATCH 18/18] MAINTAINERS - Add file pattern to CISCO FCOE HBA DRIVER Joe Perches
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=20090527055005.GA9802@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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