Perhaps times have changed enough that I can revive this idea from a
few years ago:
<quote year=1999>
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.
</quote>
The patch now appends patches as -name rather than +name to avoid
issues that might exist with packaging tools and scripts.
diff -urN -x genksyms -x '*.ver' -x '.patch*' -x '*.orig' orig/Makefile patched/Makefile
--- orig/Makefile 2003-07-29 13:31:50.000000000 -0500
+++ patched/Makefile 2003-07-29 15:25:36.000000000 -0500
@@ -25,7 +25,10 @@
# descending is started. They are now explicitly listed as the
# prepare rule.
-KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
+PATCHES=$(shell find -maxdepth 1 -name 'patchdesc.*[^~]' -printf '+%f' | \
+ sed -e 's/+patchdesc\./-/g')
+KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)$(PATCHES)
+
# SUBARCH tells the usermode build what the underlying arch is. That is set
# first, and if a usermode build is happening, the "ARCH=um" on the command
@@ -504,7 +507,7 @@
)
endef
-include/linux/version.h: Makefile
+include/linux/version.h: Makefile patchdesc.*
$(call filechk,version.h)
# ---------------------------------------------------------------------------
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - 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/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:42 EST