From: fraga@abusar.org ( Dâniel Fraga)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.9-rc1
Date: Tue, 24 Aug 2004 22:11:31 -0300 [thread overview]
Message-ID: <3j5tv1-ec2.ln1@tux.abusar.org> (raw)
In-Reply-To: 412BDC86.8000608@sover.net
In article <412BDC86.8000608@sover.net>,
Stephen Wille Padnos <spadnos@sover.net> writes:
> You wouldn't have to. The patch method from 2.6.8.x to 2.6.8.x+1 would
> be this:
> unpatch 2.6.8.x
> patch 2.6.8.x+1
> Actually, going from any patch sublevel to any other is the same two
> steps: remove the last patch level, patch to the new level.
Ok, I got it. So we have to do this:
1) If I have 2.6.8 and I want upgrade it to 2.6.8.1, I apply the
2.6.8.1 patch
2) If I have 2.6.8.1 and I want upgrade it to 2.6.8.2, I have to remove
2.6.8.1, so it can go back to 2.6.8 and I can apply the 2.6.8.2
directly on the 2.6.8 kernel. This is valid for any 2.6.8.x version for
instance...
3) Finally, if I have 2.6.8.x kernel and I want upgrade it to 2.6.9, I
can just remove the 2.6.8.x patch and apply 2.6.9 on 2.6.8 as I'm used
to do.
Ok, it seems reasonable now. Thank you very much.
--
http://Processo.tk (1001 dias)
http://U-br.tk
Linux 2.6.7
São Paulo - SP
next prev parent reply other threads:[~2004-08-25 1:30 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 7:49 Linux 2.6.9-rc1 Linus Torvalds
2004-08-24 16:40 ` Linux 2.6.9-rc1 (compile stats) John Cherry
2004-08-24 16:41 ` Linux 2.6.9-rc1 Pierre Ossman
2004-08-24 16:46 ` Russell King
2004-08-24 16:59 ` Pierre Ossman
2004-08-24 17:50 ` Alexander Gran
2004-08-24 18:42 ` Matt Mackall
2004-08-24 19:23 ` Linus Torvalds
2004-08-24 19:38 ` Chris Meadors
2004-08-24 19:54 ` Florian Weimer
2004-08-24 20:13 ` Josh Boyer
2004-08-24 20:25 ` Jesper Juhl
2004-08-24 20:07 ` Tim Schmielau
2004-08-24 20:32 ` Matt Mackall
2004-08-24 21:22 ` Martin J. Bligh
2004-08-24 22:55 ` Dave Hansen
2004-08-24 22:52 ` H. Peter Anvin
2004-08-24 23:46 ` Dâniel Fraga
2004-08-25 0:11 ` Daniel Andersen
2004-08-25 1:01 ` Dâniel Fraga
2004-08-25 4:24 ` H. Peter Anvin
2004-08-25 20:36 ` Bill Davidsen
2004-08-25 0:25 ` Stephen Wille Padnos
2004-08-25 1:11 ` Dâniel Fraga [this message]
2004-08-25 9:13 ` Geert Uytterhoeven
2004-08-25 20:18 ` Bill Davidsen
2004-08-24 18:54 ` Chris Wedgwood
2004-08-24 21:48 ` H. Peter Anvin
2004-08-24 21:58 ` Randy.Dunlap
2004-08-25 14:45 ` Chris Friesen
2004-08-25 16:12 ` Matthias Andree
2004-08-25 18:52 ` Joshua Kwan
2004-08-25 20:32 ` Harald Welte
2004-08-25 20:32 ` Harald Welte
2004-08-25 21:35 ` Henrik Nordstrom
2004-08-25 23:48 ` Harald Welte
2004-08-25 23:44 ` David S. Miller
2004-08-25 23:44 ` David S. Miller
2004-08-26 3:14 ` Joshua Kwan
2004-08-26 8:02 ` Harald Welte
2004-08-26 8:02 ` Harald Welte
2004-08-26 5:07 ` Mark Lord
[not found] ` <20040825231407.058b3ea6.davem@redhat.com>
2004-08-26 6:15 ` David S. Miller
2004-08-31 17:34 ` 2.6.9-rc1: missing netfilter help texts Adrian Bunk
2004-08-31 18:40 ` [netfilter-core] " Harald Welte
2004-08-31 18:40 ` Harald Welte
2004-09-02 1:31 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 0:31 Linux 2.6.9-rc1 Sartorelli, Kevin
2004-08-25 1:05 ` Daniel Andersen
2004-08-25 1:20 ` Linus Torvalds
2004-08-25 14:52 ` Martin J. Bligh
2004-08-25 21:14 ` Roman Zippel
2004-08-26 8:09 ` Denis Vlasenko
2004-08-26 8:35 ` Geert Uytterhoeven
2004-08-27 12:45 ` Horst von Brand
2004-08-27 21:30 ` Denis Vlasenko
2004-08-25 20:27 ` Bill Davidsen
2004-08-25 22:20 David Mansfield
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=3j5tv1-ec2.ln1@tux.abusar.org \
--to=fraga@abusar.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.