[lkml]   [2003]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RFC: a code slush for 2.5?
On Mon, 3 Feb 2003, Jeff Garzik wrote:

> Specific areas I think deserve attention before "nothing but bug fixes"
> includes a lot of driver implementation and testing for the driver
> model. Pat's given us some cool stuff... that isn't used very much so
> far. There are some key implementation decisions in that area that need
> to be made, before a lot of that can be used, too. Power Management is
> another area. That sorta fell by the wayside, IMO, but _is_ doable
> given the current infrastructure that 2.5 now has. klibc is yet another
> thing that needs tackling.
> Maybe I am coming from a "driver guy" bias, but it seems like calling a
> code freeze is premature. I know everybody's chomping at the bit for
> 2.6 to be released, already, gosh darn it. But please consider this
> pause, as well.
> So, if I had to make the proposal concrete, I would propose:
> "code slush" effective immediately
> code freeze, Easter holiday (April 19?)
> Comments/curses?

It would be wise if a freeze was delayed until after at least IDE and
console switching both work reliably with preempt enabled.


Gerhard Mack

<>< As a computer I find your faith in technology amusing.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.069 / U:2.684 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site