> This four-line patch provides a means for listing what patches have been
> built into a kernel. This will help track non-standard kernel versions,
> such as those released by Redhat, or Alan's ac series, etc. more easily.
>
> With this patch in place, each new patch can include a file of the form
> "patchname.[identifier]" in the top level source directory and
> [identifier] will then be added to the kernel version string. For
> instance, Alan's ac patches could include a file named patchdesc.ac2
> (containing a change log, perhaps), and the resulting kernel would be
> identified as 2.2.0-pre6+ac2, both at boot and by uname.
>
> This may prove especially useful for tracking problems with kernels built
> by distribution packagers and problems reported by automated tools.
I just want to second this. I think it is very usefull to list
patches: we are approaching stable series and there are lots of
patches for stable series.
Perhaps searching only Documentation/ tree would be sufficient? (After
all, description of patch is just form of documentation, don't you
think?)
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- 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/