From: "T. Weyergraf" <kirk@colinet.de>
To: linux-kernel@vger.kernel.org
Cc: kirk@colinet.de
Subject: patch-2.6.9 against 2.6.8.1
Date: Tue, 19 Oct 2004 09:23:23 +0200 (CEST) [thread overview]
Message-ID: <200410190723.i9J7NNuv027374@hydra.colinet.de> (raw)
Hi all,
I just build 2.6.9 using the patch-2.6.9, as always. Previously,
I was using 2.6.8.1 and i expected patch-2.6.9 to work on the
2.6.8.1 tree.
The patch-2.6.9 is somewhat "confused". Against 2.6.8.1, it fails
to change the SUBLEVEL field:
<snip>
@@ -1,6 +1,6 @@
VERSION = 2
PATCHLEVEL = 6
-SUBLEVEL = 8
+SUBLEVEL = 9
EXTRAVERSION =
NAME=Zonked Quokka
</snip>
As one can see, the patch failes, since in 2.6.8.1, EXTRAVERSION is set
to 1. Also, patch-2.6.9 contains the small fixes in fs/nfs/file.c, that
were given in patch-2.6.8.1.
Is this the desired behaviour ? Based on the past, i expected new
patches to go against the latest stable kernel ( which is reported
2.6.8.1 by kernel.org ). Will - in the future - new patches skip the
4-digit kernelpatches ?
I do not intent to start a flamewar over whether 4-digit kernelreleases
are the right/wrong way to go. I am just looking for a consistent
behaviour, which is at this point only given, if you expect new
kernelreleases to go against the last 3-digit release.
Is that so ?
Regards,
Thomas Weyergraf
--
Thomas Weyergraf kirk@colinet.de
Funny IA64 Opcode Dept: ( see arch/ia64/lib/memset.S )
"br.ret.spnt.few" - got back from getting beer, did not spend a lot.
next reply other threads:[~2004-10-19 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 7:23 T. Weyergraf [this message]
2004-10-19 7:38 ` patch-2.6.9 against 2.6.8.1 Buddy Lucas
2004-10-19 16:43 ` Jesper Juhl
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=200410190723.i9J7NNuv027374@hydra.colinet.de \
--to=kirk@colinet.de \
--cc=linux-kernel@vger.kernel.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