Skip to content

Commit

Permalink
[PATCH] Add text for dealing with "dot releases" to README
Browse files Browse the repository at this point in the history
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 <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
  • Loading branch information
kurtwall authored and Linus Torvalds committed Jul 27, 2005
1 parent e5c2d74 commit 896e551
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 896e551

Please sign in to comment.