From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, pcnet32@verizon.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] [374/2many] MAINTAINERS - PCNET32 NETWORK DRIVER
Date: Sun, 12 Aug 2007 23:46:49 -0700 [thread overview]
Message-ID: <1186987609.10249.22.camel@localhost> (raw)
In-Reply-To: <20070812.233630.00455011.davem@davemloft.net>
On Sun, 2007-08-12 at 23:36 -0700, David Miller wrote:
> Ok, 374 patches is just rediculious.
>
> So many patches eats up an enormous amount of mailing list resources,
> and for these patches in particular there are few reasons to split
> them up at all. The fact that the split up landed you at 300+ patches
> is a very good indication of that.
More than ridiculous. Completely agree.
I tried to send 1 patch over the last couple of days.
Unfortunately, it's > 100KB and disappears into the void.
How about 10 patches or so?
What about maintainer sign offs?
Personally, I don't think it's necessary, but for
the subsystem maintainers like you, if or when the
get_maintainers.pl get integrated into patch
generation mechanisms, you might get more emails.
Perhaps more than you want.
Suggestions?
One good thing by emailing all the listed maintainers,
I've gotten several bounces for invalid addresses.
next prev parent reply other threads:[~2007-08-13 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:33 [PATCH] [374/2many] MAINTAINERS - PCNET32 NETWORK DRIVER joe
2007-08-13 6:36 ` David Miller
2007-08-13 6:46 ` Joe Perches [this message]
2007-08-13 7:18 ` Al Viro
2007-08-13 13:11 ` Hans-Jürgen Koch
2007-08-13 7:18 ` David Miller
2007-08-13 7:22 ` Joe Perches
2007-08-13 12:08 ` Jiri Kosina
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=1186987609.10249.22.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
--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;
as well as URLs for NNTP newsgroup(s).