On Sat, Dec 15, 2001 at 02:18:35PM -0500, Jeff Garzik wrote:
> Andre Hedrick wrote:
> > Well blame that on the folks that are not taking kernel code that will
> > allow you to solve this problem. Linus is the number one offender.
> Linus is taking some patches and not others right now... so what? A
> couple of my patches, isolated and clearly unrelated to bio and mochel's
> driver work, made it in. Others got dropped.
Patches that are unrelated to bio and obviously correct shouldn't be dropped
indefinately, or if they're being deferred, then $maintainer should say so.
> I do not believe this as a personal condemnation of your patches, or
> bcrl's, or anyone else's.
> Patience is a virtue ;-) We have a long devel series in front of us
> and we are only at the pre-patches to the FIRST 2.5.x release.
There is no reason not to have a 6 month devel cycle, and plenty of reasons
in favour of it. If people aren't going to bother reviewing patches in a
timely fashion, they should tell people when a good time to resend patches
is. Given the whole vm fiasco in 2.4 (which is still a mess and falling
apart for heavy loads) which stems from a lot of random direction with
patches, I hope that some of the underlying problems will get fixed. But
it really doesn't look that way.
-- Fish. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:30 EST