From: David Miller <davem@davemloft.net>
To: pavel@ucw.cz
Cc: ebiederm@xmission.com, baolex.ni@intel.com, pablo@netfilter.org,
kaber@trash.net, kadlec@blackhole.kfki.hu, jmorris@namei.org,
yoshfuji@linux-ipv6.org, m.szyprowski@samsung.com,
kyungmin.park@samsung.com, k.kozlowski@samsung.com,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
johunt@akamai.com, vpai@akamai.com, chuansheng.liu@intel.com,
aryabinin@virtuozzo.com
Subject: Re: [PATCH 1115/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 02 Aug 2016 10:59:01 -0700 (PDT) [thread overview]
Message-ID: <20160802.105901.1278960621806579606.davem@davemloft.net> (raw)
In-Reply-To: <20160802174733.GB4628@amd>
From: Pavel Machek <pavel@ucw.cz>
Date: Tue, 2 Aug 2016 19:47:33 +0200
> But that does not make me like the series. And yes, hiding backdoor
> in one of those would be way too easy...
This is one of the worst patch series submissions in history.
At vger.kernel.org postmaster I just spent 45 minutes dealing
with the fallout.
1200+ patches all at once, unacceptable.
Every patch having the same Subject line text, unacceptable.
Triggering rate limiting bounces on %50+ of all lkml recipients,
unacceptable.
This is why you don't spam lists with a thousand patches.
If this is going to be properly submitted, it must be done in
reasonable, bite size, pieces of 10 to 15 patches at a time.
prev parent reply other threads:[~2016-08-02 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:17 [PATCH 1115/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-02 14:29 ` Eric W. Biederman
2016-08-02 17:47 ` Pavel Machek
2016-08-02 17:59 ` David Miller [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=20160802.105901.1278960621806579606.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aryabinin@virtuozzo.com \
--cc=baolex.ni@intel.com \
--cc=chuansheng.liu@intel.com \
--cc=coreteam@netfilter.org \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=johunt@akamai.com \
--cc=k.kozlowski@samsung.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pavel@ucw.cz \
--cc=vpai@akamai.com \
--cc=yoshfuji@linux-ipv6.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).