* [PATCH] README - Explain new 2.6.xx.x bug-fix release numbering scheme
@ 2004-08-27 12:39 Daniel Andersen
2004-08-27 12:56 ` Maciej Soltysiak
0 siblings, 1 reply; 2+ messages in thread
From: Daniel Andersen @ 2004-08-27 12:39 UTC (permalink / raw)
To: linux kernel mailing list
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
--- linux/README.orig 2004-08-14 07:37:40.000000000 +0200
+++ linux/README 2004-08-27 14:37:09.242341334 +0200
@@ -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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] README - Explain new 2.6.xx.x bug-fix release numbering scheme
2004-08-27 12:39 [PATCH] README - Explain new 2.6.xx.x bug-fix release numbering scheme Daniel Andersen
@ 2004-08-27 12:56 ` Maciej Soltysiak
0 siblings, 0 replies; 2+ messages in thread
From: Maciej Soltysiak @ 2004-08-27 12:56 UTC (permalink / raw)
To: linux kernel mailing list
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-08-27 12:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-27 12:39 [PATCH] README - Explain new 2.6.xx.x bug-fix release numbering scheme Daniel Andersen
2004-08-27 12:56 ` Maciej Soltysiak
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®