From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] final scsi updates for 2.6.34-rc1
Date: Fri, 12 Mar 2010 10:34:30 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003121028390.3719@i5.linux-foundation.org> (raw)
In-Reply-To: <1268418441.2802.61.camel@mulgrave.site>
On Fri, 12 Mar 2010, James Bottomley wrote:
>
> I'm not objecting to a shorter merge window, just the unpredictability
> of all of this.
If you read the 2.6.33 release notes, the unpredictability WAS THE WHOLE
F*CKING POINT!
I'm tired of people being able to predict exactly when the merge window
closes, and then using that to make the last days of the merge window be
hell on me, and sending all the merges within about 24 hours of the
closing.
So I'm not doing it.
If you had the major changes ready when the merge window opened, you
should damn well have sent it in _then_.
End of story. I've told people before. The merge window is for _merging_,
not for doing development. If you send me something the last day, then
there is no "window" any more. And It is _really_ annoying to have fifty
pull requests on the last day. I'm not going to take it any more.
And the thing is, all your explanations make things WORSE. You're
basically saying that you're working exactly the way that I'm not going to
accept.
So you're now going to get to wait six or seven weeks, because I refuse to
work the way you have worked me for the last two years. I gave people a
heads-up, and I probably shouldn't have. Some people noticed. And other
people didn't even care, because they never gamed the system in the first
place.
And some people - like you - both gamed the system, and didn't read the
release notes, and now you complain. Tough.
And the fact that you complain about the very fact that you were gaming
the system and now you can't because it's not predictable enough to game
is what just proves my f*cking point!
Linus
next prev parent reply other threads:[~2010-03-12 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 17:36 James Bottomley
2010-03-12 18:10 ` Linus Torvalds
2010-03-12 18:27 ` James Bottomley
2010-03-12 18:34 ` Linus Torvalds [this message]
2010-03-12 18:40 ` Linus Torvalds
2010-03-13 19:35 ` Ray Lee
2010-03-13 20:16 ` Douglas Gilbert
2010-03-16 17:11 James Bottomley
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.LFD.2.00.1003121028390.3719@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®