[PATCH] Add text for dealing with "dot releases" to README
From: Kurt Wall
Date: Tue Jul 26 2005 - 20:36:54 EST
The emergence of so-called "dot releases" that are non-incremental
patches against a base kernel requires different handling of patches
(revert previous patches before applying the newest one). This patch
adds a paragrach to $TOPDIR/README explaining how to do deal with
dot release patches.
The patch is against 126.96.36.199. A possibly too quick glance at
MAINTAINERS didn't show one for README.
Signed-off-by: Kurt Wall <kwall@xxxxxxxxxxxxx>
--- linux-188.8.131.52/README 2005-07-26 21:18:18.000000000 -0400
+++ b/README 2005-07-26 21:25:13.000000000 -0400
@@ -87,6 +87,16 @@
kernel source. Patches are applied from the current directory, but
an alternative directory can be specified as the second argument.
+ - If you are upgrading between releases using the stable series patches
+ (for example, patch-2.6.xx.y), note that these "dot-releases" are
+ not incremental and must be applied to the 2.6.xx base tree. For
+ example, if your base kernel is 2.6.12 and you want to apply the
+ 184.108.40.206 patch, you do not and indeed must not first apply the
+ 220.127.116.11 and 18.104.22.168 patches. Similarly, if you are running kernel
+ version 22.214.171.124 and want to jump to 126.96.36.199, you must first
+ reverse the 188.8.131.52 patch (that is, patch -R) _before_ applying
+ the 184.108.40.206 patch.
- Make sure you have no stale .o files and dependencies lying around:
The first myth of management is that it exists. The second myth of
management is that success equals skill.
-- Robert Heller
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/