[lkml]   [1998]   [Oct]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.1.123 and fbcon.c
In <>, on
at 10:11 AM, John Alvord <> said:

>I don't see how a push button response is possible. In the simplest
>cases, a patch must be examined closely, the context has to be
>understood, possible ramifications explored, the patch has to be applied
>to a kernel, the kernel has to build and work. Discovering whether it
>"works" is another whole matter: some patches need special
>environments,benchmarking, evaluation of results. Some patches need
>external testing. Only after a (potentially) long process can a patch be

You can normally not have an immediate response like
"patch accepted into next version", but you can certainly have immediate
responses like:

"rejected - no documentation, what *is* this?"
"rejected - code freeze"
"rejected - no time, make new patch for the next version"
"I'll try this. If you see it in the next release it means it got in."

Helge Hafting

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

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