From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.11.1
Date: Sat, 05 Mar 2005 16:49:58 -0500 [thread overview]
Message-ID: <200503051649.58709.gene.heskett@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0503051316510.2304@ppc970.osdl.org>
On Saturday 05 March 2005 16:17, Linus Torvalds wrote:
>On Sat, 5 Mar 2005, Russell King wrote:
>> On Sat, Mar 05, 2005 at 09:40:59AM -0800, Linus Torvalds wrote:
>> > I love BK, but what BK does well is merging and maintaining
>> > trees full of good stuff. What BK sucks at is experimental stuff
>> > where you don't know whether something should be eventually used
>> > or not.
>>
>> Wait a minute - why would stuff going into 2.6.x.y be
>> "experimental" stuff? Wasn't stability the whole point of this
>> tree?
>
>The point being that _before_ a patch gets accepted, it's in that
> "limbo" state, waiting for people to veto it or say "yes".
>
>That limbo state is not well done with BK.
>
> Linus
What he said! Perfectly good patches, which fix real problems would
appear to be sitting in testing/broken_out till bit rot or ???.
If you want a testers testimony, I'm running the bk-ieee1394.patch,
and all I can say at this point is that it Just Works(TM). I have
NDI how it got a yesterdays Mar 4) date in the directory listing
there though, I've had it a bit longer than that by 2-3 days as my
copy shows a Mar 1 date. I first got it via svn fetch at
linux-ieee1394.org or some such in January.
Fixes for real problems that fix real problems should somehow get a
faster track into final. The current firewire in the kernel as of
2.6.11 is still badly borked.
If that diff in the dates means I should update and retest, please
advise.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2005-03-05 21:50 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 17:53 Greg KH
2005-03-04 17:53 ` Greg KH
2005-03-04 20:34 ` Ian Pilcher
2005-03-04 22:29 ` Greg KH
2005-03-04 20:44 ` Andrew Morton
2005-03-04 20:58 ` Greg KH
2005-03-04 21:15 ` Andrew Morton
2005-03-04 21:43 ` Greg KH
2005-03-04 21:54 ` Andrew Morton
2005-03-04 22:08 ` Greg KH
2005-03-04 21:53 ` Linus Torvalds
2005-03-04 21:59 ` Andrew Morton
2005-03-04 22:05 ` Greg KH
2005-03-04 22:36 ` Andrew Morton
2005-03-05 0:06 ` Greg KH
2005-03-05 0:28 ` Linus Torvalds
2005-03-05 7:53 ` Dave Jones
2005-03-06 5:05 ` Greg KH
2005-03-05 1:37 ` Jeff Garzik
2005-03-06 5:03 ` Greg KH
2005-03-05 9:51 ` Russell King
2005-03-05 17:19 ` Jeff Garzik
2005-03-05 17:40 ` Linus Torvalds
2005-03-05 17:46 ` Russell King
2005-03-05 21:17 ` Linus Torvalds
2005-03-05 21:49 ` Gene Heskett [this message]
2005-03-05 22:06 ` Lee Revell
2005-03-05 23:26 ` Gene Heskett
2005-03-07 17:18 ` Alan Cox
2005-03-08 20:16 ` Lee Revell
2005-03-05 17:50 ` Jeff Garzik
2005-03-05 18:22 ` Randy.Dunlap
2005-03-05 0:24 ` Jeff Garzik
2005-03-04 21:15 ` Trond Myklebust
2005-03-04 21:33 ` Jeff Garzik
2005-03-04 21:51 ` Andrew Morton
2005-03-04 21:58 ` Jeff Garzik
2005-03-05 7:11 ` James Bourne
2005-03-08 22:07 ` Bill Davidsen
2005-03-08 22:41 ` Chris Wright
2005-03-04 21:50 ` Dave Jones
2005-03-04 23:35 ` Andries Brouwer
2005-03-04 20:48 ` Steven Rostedt
2005-03-04 20:53 ` Greg KH
2005-03-04 21:02 ` Steven Rostedt
2005-03-05 18:32 ` L. A. Walsh
2005-03-04 19:28 Paolo
2005-03-04 19:55 ` Greg KH
2005-03-04 20:01 ` Paolo
2005-03-04 20:00 ` Jeff Garzik
2005-03-05 6:16 Shawn Starr
2005-03-06 5:06 ` Greg KH
2005-03-07 4:01 ` Shawn Starr
2005-03-07 3:58 ` Randy.Dunlap
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=200503051649.58709.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-kernel@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®