I have no idea. I don't have time to sort out 2.0,but i do have time to
review a 2.0.39 suggested set from someone who is willing to do all the leg
work.
> (Oh, and what "other chunk of bugs" are you talking about?! If this chunk
> is very great, I might get cold feet...)
I have an in queue of about 20 items from 2.0.37 stuff - mostly driver updates.
>
> > > There are a LOT of people still using v2.0.xx systems, and releasing a fix
> > > would show them that we really care.
> >
> > Im working on the basis of only caring about external exploitable holes.
>
> Well, that's rational, I can agree to that. Can't help that I'm a little
> pedantic sometimes, I guess.
>
> Then again, there are probably tons of ways to crash a v2.0.xx kernel that
> won't get fixed. But this one has gotten quite some attention, that's why
> I want it fixed. There are probably a few more such.
>
>
> /David
> _ _
> // David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
> // Project MCA Linux hacker // Dance across the winter sky //
> \> http://www.acc.umu.se/~tao/ </ Full colour fire </
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/