From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: common sense...
Date: Tue, 14 Apr 2015 13:53:14 -0400 (EDT) [thread overview]
Message-ID: <20150414.135314.1465420305300685251.davem@davemloft.net> (raw)
None of you guys seem to have it.
When the merge window opens up, you all should be putting your foot on
the break pedal.
But the vast majority of you seem to think this is the exact moment
to step as hard as possible on the gas pedal and bomb me with more
things.
This is starting to get really annoying.
I am allowing only Jeff Kirsher to send me two pull requests because
he had Intel stuff pending that got delayed due to conditions outside
of his control.
But anyone else sending me new things from this point forward will
be immediately marked as "deferred" in patchwork and therefore require
a resubmission when net-next opens back up in the future.
I don't think any of you have any idea what it's like when the merge
window opens up for me, because if you did all of you would shut your
email clients off and stop sending me stuff. The merge window is
hard enough as it is, _don't_ make it harder for me by piling more
and more stuff on my plate during this time.
Thanks.
reply other threads:[~2015-04-14 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150414.135314.1465420305300685251.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.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).