From: Daniel Andersen <anddan@linux-user.net>
To: fraga@abusar.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.9-rc1
Date: Wed, 25 Aug 2004 02:11:50 +0200 [thread overview]
Message-ID: <412BD946.1080908@linux-user.net> (raw)
In-Reply-To: <cggjvs$bv9$1@sea.gmane.org>
Dâniel Fraga wrote:
> In article <Pine.LNX.4.58.0408241221390.17766@ppc970.osdl.org>,
> Linus Torvalds <torvalds@osdl.org> writes:
>
>
>>Any reason for your preference?
>
>
> Linus, sorry but I can't agree with your decision.
>
> I'm not a developer, just an user and for me at least, there's no
> sense in supplying a patch related do 2.6.8 instead of 2.6.8.1.
>
> I always update my kernel when the official patch is announced and
> I'd expect to follow a well defined order (2.6.8 -> 2.6.8.1 ->
> 2.6.9...).
>
> Suppose we had 2.6.8.1, 2.6.8.2, 2.6.8.3 until 2.6.8.10. Should I
> remove 10 patches just to update to 2.6.9? For me it's a waste of time.
>
> I know you kernel developers use BK or some other method, but...
>
> Thanks.
>
As Linus initially said, there is the possibility of releasing a bug-fix
patch 2.6.8.2 *after* 2.6.9 has been released. This can make things very
confusing when patch-2.6.9 is against 2.6.8.1 and not 2.6.8.2 (or
2.6.8). So if we use a rule of always patching against the first x.y.Z
release (and not the last x.y.z.W by the time the new x.y.Z is released)
we can assure consistence in the patch management.
Daniel Andersen
--
next prev parent reply other threads:[~2004-08-25 0:11 UTC|newest]
Thread overview: 53+ 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 [this message]
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
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 21:35 ` Henrik Nordstrom
2004-08-25 23:48 ` Harald Welte
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 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
-- 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=412BD946.1080908@linux-user.net \
--to=anddan@linux-user.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox