From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Maintainer abuse
Date: Sat, 13 Dec 2014 00:24:03 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1412130016090.16494@nanos> (raw)
I'm really starting to get seriously grumpy about this.
Everyone is aware that we are in the middle of the merge window. So
this is definetely NOT the time to send anything else than urgent
bugfixes or the usual question/reply on something which was discussed
before.
I really consider it to be maintainer abuse to have
[PATCH V5 00/23] Generic BMIPS kernel
[RFC][PATCH 0/8] x86, mpx: Support 32-bit binaries on 64-bit kernels
[v3 00/26] Add VT-d Posted-Interrupts support
i.e. 57 patches to look at in my inbox TODAY in the middle of the
merge window where I have to make other really more urgent
decisions.
Not to talk about the other patch series which arrived in the past few
days after the merge window opened. That sums up to a total of more
than 200 patches, some of them superseeded by now.
Nothing of this is 3.19 material so posting it right now is just
useless. I'm not going to look at it and I'm not going to look at it
next week either.
This whole featuritis driven 'post crap as fast as you can' thing has
to stop, really. I'm observing the following patterns in a
frightingly increasing way:
- Posting of massive patch sets right during or just before the merge
window
- Reposting of patchsets before the reviewer/maintainer had a chance
to reply to ALL of N patches
This really has to stop.
Yours grumpy
tglx
next reply other threads:[~2014-12-12 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 23:24 Thomas Gleixner [this message]
2014-12-12 23:43 ` Borislav Petkov
2014-12-13 13:52 ` One Thousand Gnomes
2014-12-13 17:46 ` Borislav Petkov
2014-12-15 11:15 ` Thomas Gleixner
2014-12-16 2:47 ` Brian Norris
2014-12-18 10:14 ` patch tracking tools (was Re: Maintainer abuse) Paolo Bonzini
2014-12-18 13:25 ` Fam Zheng
2014-12-19 11:30 ` Paolo Bonzini
2014-12-16 8:06 ` Maintainer abuse Benjamin Herrenschmidt
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=alpine.DEB.2.11.1412130016090.16494@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®