From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2
Date: Tue, 07 Aug 2007 11:31:11 -0500 [thread overview]
Message-ID: <1186504271.3414.34.camel@localhost.localdomain> (raw)
In-Reply-To: <46B89BE7.8090903@garzik.org>
On Tue, 2007-08-07 at 12:20 -0400, Jeff Garzik wrote:
> James Bottomley wrote:
> > I'm arguing that a too strict an interpretation of bugfix only post -rc1
> > will damage feature stabilisation. Please think carefully about this.
> > If we go out in a released kernel with a problematic user space ABI, we
> > end up being committed to it forever.
>
>
> IMO you're going off on your own tangent. Linus never singled out bsg
> (far from it, in fact, since bsg was not a major LOC contributor) or
> declared ABI-related fixes verboten.
>
> I don't think anyone wants to release a userspace ABI with problems,
> since we all know that's basically locked in stone once its in a
> mainline release.
>
> AFAICS his main complaint was he felt your push was a big honking huge
> change, late in the game, that included obvious non-fixes. And it was.
> lpfc was probably the biggest part of that, not bsg, and it's pretty
> clear such a big lpfc update should have gone in when the merge window
> was open. The [non-lpfc] cleanups were also not -rc2 material.
I think you'll find that part of the complaint was addressed in the
first part of the email which you didn't quote.
James
next prev parent reply other threads:[~2007-08-07 16:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 17:31 [GIT PATCH] scsi bug fixes for 2.6.23-rc2 James Bottomley
2007-08-07 0:51 ` Linus Torvalds
2007-08-07 3:55 ` James Bottomley
2007-08-07 4:01 ` Linus Torvalds
2007-08-07 13:12 ` James Smart
2007-08-07 16:13 ` Jeff Garzik
2007-08-07 14:31 ` James Bottomley
2007-08-07 16:20 ` Jeff Garzik
2007-08-07 16:31 ` James Bottomley [this message]
2007-08-07 7:14 ` Andrew Morton
2007-08-07 13:58 ` FUJITA Tomonori
2007-08-07 14:21 ` Jeff Garzik
2007-08-07 17:47 ` Andrew Morton
2007-08-07 14:25 ` James Bottomley
2007-08-07 14:55 ` Alan Cox
2007-08-07 14:56 ` Jeff Garzik
2007-08-07 15:11 ` Jeff Garzik
2007-08-07 15:38 ` James Bottomley
2007-08-07 15:43 ` Jeff Garzik
2007-08-07 17:51 ` Andrew Morton
2007-08-13 12:42 ` Jens Axboe
2007-08-13 15:58 ` Jeff Garzik
2007-08-13 18:02 ` Jens Axboe
2007-08-13 18:07 ` Jens Axboe
2007-08-07 15:24 ` Jeff Garzik
2007-08-07 14:53 ` Rene Herman
2007-08-07 16:06 ` Jeff Garzik
2007-08-07 16:27 ` James Smart
2007-08-07 16:34 ` Jeff Garzik
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=1186504271.3414.34.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.