From: David Miller <davem@davemloft.net>
To: joe@perches.com
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:36:30 -0700 (PDT) [thread overview]
Message-ID: <20070812.233630.00455011.davem@davemloft.net> (raw)
In-Reply-To: <46bffb4c.nrqicrPs7IJXlgQ0%joe@perches.com>
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.
next prev parent reply other threads:[~2007-08-13 6:36 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 [this message]
2007-08-13 6:46 ` Joe Perches
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=20070812.233630.00455011.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--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).