From: Lukasz <el.es.cr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES
Date: Mon, 4 Jul 2011 13:15:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20110704T150945-305@post.gmane.org> (raw)
In-Reply-To: <20110704085126.GI19426@pcarmody2.research.nokia.com>
Phil Carmody <ext-phil.2.carmody <at> nokia.com> writes:
> Yeah, I was wondering how to do that. The idea of cc:ing about 30
> people for the whole set seemed a bit too spammy, and wasn't sure if
> individually-selected cc:lists for eack of the patches made sense.
> The alternative was to make it 7 (or more...) independent patchsets,
> but that turned the task into too much of a game of chess. I chickened
> out of thinking more, and cowardly went for the 'trivial' route.
>
There is a script that parses MAINTAINERS (and AFAIR not only that) that
gives you a list of people responsible (and their emails) :)
( linux/scripts/get_maintainer.pl )
L.
prev parent reply other threads:[~2011-07-04 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 21:47 [PATCH 0/7] [TRIVIAL] Cleanup spurious CONFIGs Phil Carmody
2011-07-02 21:47 ` [PATCH 1/7] mn10300: there is no CONFIG_CALIBRATE_DELAY Phil Carmody
2011-07-02 21:47 ` [PATCH 2/7] cris: there is no CONFIG_ETRAX_KGB_PORT2 Phil Carmody
2011-07-02 21:47 ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Phil Carmody
2011-07-02 21:47 ` [PATCH 4/7] ppc: there is no CONFIG_PPC47x Phil Carmody
2011-07-02 21:47 ` [PATCH 5/7] ppc: there is no CONFIG_PPC_CPU Phil Carmody
2011-07-02 21:47 ` [PATCH 6/7] nommu: there is no CONFIG_SMALL_TASKS Phil Carmody
2011-07-02 21:47 ` [PATCH 7/7] xtensa: there is no CONFIG_UNALIGNED_USER Phil Carmody
2011-07-04 4:58 ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Dave Chinner
2011-07-04 8:51 ` Phil Carmody
2011-07-04 13:15 ` Lukasz [this message]
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=loom.20110704T150945-305@post.gmane.org \
--to=el.es.cr@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®