From: Kurt Wall Date: Wed, 27 Jul 2005 18:45:20 +0000 (-0700) Subject: [PATCH] Add text for dealing with "dot releases" to README X-Git-Tag: firefly_0821_release~42584^2~65 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=896e5518da74f9d20db8163526014fba16b1f2b4;p=firefly-linux-kernel-4.4.55.git [PATCH] Add text for dealing with "dot releases" to README 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. Signed-off-by: Kurt Wall Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/README b/README index 0df20f07227b..76dd780d88ed 100644 --- a/README +++ b/README @@ -87,6 +87,16 @@ INSTALLING the kernel: 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 + 2.6.12.3 patch, you do not and indeed must not first apply the + 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel + version 2.6.12.2 and want to jump to 2.6.12.3, you must first + reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying + the 2.6.12.3 patch. + - Make sure you have no stale .o files and dependencies lying around: cd linux