From: Daniel Andersen <anddan@linux-user.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@osdl.org
Subject: [PATCH] README (resend) - Explain new 2.6.xx.x version number
Date: Tue, 14 Sep 2004 23:35:15 +0200 [thread overview]
Message-ID: <41476413.1060100@linux-user.net> (raw)
This one ended up in the void last time without any comments.
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 17:16:55.107413637 +0200
@@ -76,6 +76,23 @@
the backup files (xxx~ or xxx.orig), and make sure that there are no
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. In case of a
+ bug-fix release such as if eg. 2.6.8.2 is released after 2.6.9 has
+ been released, 2.6.9 is still to be considered the newest kernel
+ release of all current kernels. Old patches can be reversed by
+ adding the "-R" option to the patch tool.
+
+ Example to apply a bugfix release patch:
+ bzip2 -dc ../patch-2.6.8.1.bz2 | patch -p1
+
+ Example to apply a new release on a bugfix tree:
+ bzip2 -dc ../patch-2.6.8.1.bz2 | patch -p1 -R
+ bzip2 -dc ../patch-2.6.9.bz2 | patch -p1
Alternatively, the script patch-kernel can be used to automate this
process. It determines the current kernel version and applies any
next reply other threads:[~2004-09-14 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 21:35 Daniel Andersen [this message]
2004-09-14 21:43 ` [PATCH] README (resend) - Explain new 2.6.xx.x version number Dave Jones
2004-09-14 22:23 ` Daniel Andersen
2004-09-15 1:02 ` Roman Zippel
2004-09-15 2:25 ` Daniel Andersen
2004-09-15 2:40 ` Randy.Dunlap
2004-09-15 8:01 ` Denis Vlasenko
2004-09-15 11:06 ` Roman Zippel
2004-09-15 15:25 ` Randy.Dunlap
2004-09-15 15:57 ` Roman Zippel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41476413.1060100@linux-user.net \
--to=anddan@linux-user.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).