From: David Miller <davem@davemloft.net> Date: 2007-08-13 10:48:44
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.
From: Joe Perches <joe@perches.com> Date: 2007-08-13 12:25:05
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.
On Sun, Aug 12, 2007 at 11:46:49PM -0700, Joe Perches wrote:
On Sun, 2007-08-12 at 23:36 -0700, David Miller wrote:
quoted
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.
So put it on anonftp/webpage/git tree and post the URI, damnit.
Of all ridiculous reasons for a mailbomb...
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.
Actually, I can see 546 patches up to now. Horrid.
Besides that, it's very unfortunate that every single mail of this
ridiculously huuuuge patch series starts a new thread (no 'References' or
'In-Reply-To' header), so it's not possible to nuke it at once in an usual
way.
--
Jiri Kosina
On Sun, Aug 12, 2007 at 11:46:49PM -0700, Joe Perches wrote:
quoted
On Sun, 2007-08-12 at 23:36 -0700, David Miller wrote:
quoted
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.
So put it on anonftp/webpage/git tree and post the URI, damnit.
Of all ridiculous reasons for a mailbomb...
Or make it 3 or 4 or even 40 patches, but not 500.
Hans