[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.999.0708061748240.5037@woody.linux-foundation.org>
Date: Mon, 6 Aug 2007 17:51:57 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: James Bottomley <James.Bottomley@...elEye.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2
On Sat, 4 Aug 2007, James Bottomley wrote:
>
> This is mainly bug fixes ... there's one or two features completions
> that have been delayed pending ack and review to do with bsg (headers
> and passthrough) but these are really required to complete already
> upstream code.
James, this is the last time *ever* I apply patches from you after -rc1.
You used to have serious problems with the merge window, but for a few
releases you then seemed to "get it" and got on with the program.
But now it's back to "anythign goes", apparently. And I'm going to take a
hard-line approach with you now.
For SCSI merges, if I don't get the first pull request in the FIRST week
of the merge window, don't bother sending one later, unless it's pure
fixes and regressions.
And after -rc1, I don't want to see crap like this:
46 files changed, 2837 insertions(+), 2050 deletions(-)
because that simply is *not* appropriate after -rc1, much less -rc2.
So I pulled, but I wanted to make it very clear that I'm very unhappy with
you right now, and you're on my shit-list for the next few releases. Get
the changes in before -rc1, or just *wait*. If they aren't ready before
the merge window opens, they simply shouldn't be merged at all.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists