lkml.org 
[lkml]   [2004]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subject[PATCH] README - Explain new 2.6.xx.x bug-fix release numbering scheme
This patch explains the new 2.6.xx.x bug-fix release numbering scheme 
introduced with 2.6.8.1. I hope this can help people understand how to
patch such kernels.

Daniel Andersen
--

diff -urN linux/README.orig linux/README
--- linux/README.orig 2004-08-14 07:37:40.000000000 +0200
+++ linux/README 2004-08-27 14:37:09.242341334 +0200
@@ -77,6 +77,13 @@
failed patches (xxx# or xxx.rej). If there are, either you or me has
made a mistake.

+ As of kernel 2.6.8 there was a bug-fix release numbering scheme
+ introduced. In such cases a fourth number is added to the release
+ version, eg. 2.6.8.1. When patching from a 2.6.xx(.x) release to a
+ newer version, patches are to be applied against the original
+ release, eg. 2.6.8 and not the bug-fix release 2.6.8.1. Old patches
+ can be reversed by adding the "-R" option to patch.
+
Alternatively, the script patch-kernel can be used to automate this
process. It determines the current kernel version and applies any
patches found.
-
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/
\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.038 / U:1.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site