From: Joe Perches <joe@perches.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/net/: Spelling fixes
Date: Mon, 17 Dec 2007 12:47:11 -0800 [thread overview]
Message-ID: <1197924431.27386.40.camel@localhost> (raw)
In-Reply-To: <1197924025.2541.11.camel@dv>
On Mon, 2007-12-17 at 15:40 -0500, Pavel Roskin wrote:
> On Mon, 2007-12-17 at 11:40 -0800, Joe Perches wrote:
> I don't think such minor comment fixes need to be reviewed by
> the maintainers. Thanks anyway.
I'd like to know who pushes what source tree sections forward.
I have a script that uses annotated MAINTAINERS sections
to forward patches to "appropriate" maintainers. That script
generated the CC's.
To me the question is who pushes.
If it's not a maintainer, who does? Anyone have list?
next prev parent reply other threads:[~2007-12-17 20:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 19:30 [PATCH] drivers/ide/: Spelling fixes Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/edac/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/firmware/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/i2c/: " Joe Perches
2007-12-17 20:32 ` Jean Delvare
2007-12-17 19:30 ` [PATCH] drivers/ide/: " Joe Perches
2007-12-17 20:53 ` Bartlomiej Zolnierkiewicz
2007-12-17 19:30 ` [PATCH] drivers/infiniband/: " Joe Perches
2007-12-18 5:48 ` Roland Dreier
2007-12-17 19:30 ` [PATCH] drivers/input/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/isdn/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/macintosh/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/media/: " Joe Perches
2007-12-17 19:30 ` [PATCH] include/media/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/message/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/mtd/: " Joe Perches
2007-12-17 19:30 ` Joe Perches
2007-12-17 19:36 ` Joe Perches
2007-12-17 19:36 ` Joe Perches
2007-12-17 19:40 ` Joe Perches
2007-12-17 19:40 ` Joe Perches
2007-12-17 19:40 ` [PATCH] drivers/net/: " Joe Perches
2007-12-17 19:40 ` Joe Perches
2007-12-17 19:58 ` Chris Snook
2007-12-17 20:56 ` Stefano Brivio
2007-12-17 20:56 ` Stefano Brivio
2007-12-17 21:15 ` Joe Perches
2007-12-17 21:15 ` Joe Perches
2007-12-17 19:40 ` Joe Perches
2007-12-17 20:40 ` Pavel Roskin
2007-12-17 20:47 ` Joe Perches [this message]
2007-12-17 20:43 ` John W. Linville
2007-12-17 20:43 ` John W. Linville
2007-12-17 21:15 ` David Woodhouse
2007-12-17 21:15 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2007-12-17 19:40 Joe Perches
2007-12-17 19:40 ` 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=1197924431.27386.40.camel@localhost \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.