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
@@ -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.

Hi,

DA> +   As of kernel 2.6.8 there was a bug-fix release numbering scheme
DA> +   introduced. In such cases a fourth number is added to the release
DA> +   version, eg. 2.6.8.1. When patching from a 2.6.xx(.x) release to a
DA> +   newer version, patches are to be applied against the original
DA> +   release, eg. 2.6.8 and not the bug-fix release 2.6.8.1. Old patches
DA> +   can be reversed by adding the "-R" option to patch.

DA> +
How about giving an example like:

    To apply a bugfix release patch:
    # cd /usr/src/linux-2.6.8
    # patch -p1 <../patch-2.6.8.1

    To apply a new release on a bugfix tree:
    # cd /usr/src/linux-2.6.8.1
    # patch -p1 -R <../patch-2.6.8.1
    # patch -p1 <../patch-2.6.9

Examples are always good.

Regards,
Maciej