Re: Linux 2.6.16.14

[Willy Tarreau <willy@w.ods.org>]

On Fri, May 05, 2006 at 03:02:47PM +1000, Nigel Cunningham wrote:
> Hi Willy.
(snip)
> 
> I didn't mention it previously - I guess because it was subconscious - but I'm 
> looking at things from the point of view of someone maintaining an 
> out-of-tree patch. With almost all of these revisions, my patch continues to 
> apply cleanly, but I still get people asking "Is the patch for 2.6.16.9" safe 
> to apply against "2.6.16.9+x"? I simply don't have the time to continually 
> test and check, but I end up feeling like there's a new 2.6.x release 
> everyday that I just have to keep up with, because that's what the stable 
> users want. Maybe it just proves that I should hurry up and get the git tree 
> finished so I get try to get Suspend2 merged :)

Oh yes, I understand your problem, I went through that for several years with
2.4. Another advantage of many small updates is that the risk of conflict is
minor, and your users might often be able to apply the official patch *after*
your patch, which is very convenient.

Maybe you should just run a cron script to patch your kernels everytime a
new fix goes out, so that you'll at least be able to reply to your users
whether it's supposed to work or not.

> Regards,
> 
> Nigel

Regards,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/