Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

[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 <kwall@kurtwerks.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  • Loading branch information...
commit 896e5518da74f9d20db8163526014fba16b1f2b4 1 parent e5c2d74
authored July 27, 2005 Linus Torvalds committed July 27, 2005

Showing 1 changed file with 10 additions and 0 deletions. Show diff stats Hide diff stats

  1. 10  README
10  README
@@ -87,6 +87,16 @@ INSTALLING the kernel:
87 87
    kernel source.  Patches are applied from the current directory, but
88 88
    an alternative directory can be specified as the second argument.
89 89
 
  90
+ - If you are upgrading between releases using the stable series patches
  91
+   (for example, patch-2.6.xx.y), note that these "dot-releases" are
  92
+   not incremental and must be applied to the 2.6.xx base tree. For
  93
+   example, if your base kernel is 2.6.12 and you want to apply the
  94
+   2.6.12.3 patch, you do not and indeed must not first apply the
  95
+   2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel
  96
+   version 2.6.12.2 and want to jump to 2.6.12.3, you must first
  97
+   reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying
  98
+   the 2.6.12.3 patch.
  99
+
90 100
  - Make sure you have no stale .o files and dependencies lying around:
91 101
 
92 102
 		cd linux

0 notes on commit 896e551

Please sign in to comment.
Something went wrong with that request. Please try again.