Messages in this thread | | | From | "Helge Hafting" <> | Date | Fri, 02 Oct 1998 09:46:13 +0100 | Subject | Re: 2.1.123 and fbcon.c |
| |
In <Pine.BSF.4.02A.9810010959070.27498-100000@earl-grey.cloud9.net>, on 10/01/98 at 10:11 AM, John Alvord <jalvo@cloud9.net> 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 >accepted.
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" or "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 majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |