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:40:50 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003121035490.3719@i5.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1003121028390.3719@i5.linux-foundation.org>
On Fri, 12 Mar 2010, Linus Torvalds wrote:
>
> 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!
Btw, just to clarify for next time: I'm not even going to mention in the
release notes how long the merge window is going to be.
Maybe I'll say "that's enough" after just one week, because the good
people did what they do, and sent me a lot of merges early, there were no
problems, and I might as well cut an -rc1 early since I have enough and
I'd like to occasionally get a _shorter_ release cycle not just because
the merge window was shorter, but because hopefully merging less might
result in an easier stabilization cycle too.
Or maybe I'll be busy for a few days, and extend it past the two weeks
just because I was in the middle of another flame war and needed a few
extra days to catch up with real work.
Who knows? The point being that being predictable has caused problems.
People have decided that they have an extra two weeks, and that the merge
window isn't a window at all, it's just a day when -rc1 gets done.
Linus
next prev parent reply other threads:[~2010-03-12 18:42 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
2010-03-12 18:40 ` Linus Torvalds [this message]
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.1003121035490.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
Powered by JetHome