From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: New dev model (was [PATCH] delete devfs)
Date: Thu, 22 Jul 2004 22:18:58 +0200 [thread overview]
Message-ID: <20040722201858.GG19329@fs.tum.de> (raw)
In-Reply-To: <20040722160112.177fc07f.akpm@osdl.org>
On Thu, Jul 22, 2004 at 04:01:12PM -0700, Andrew Morton wrote:
> Adrian Bunk <bunk@fs.tum.de> wrote:
> >
> > my personal opinon is that this new development model isn't a good
> > idea from the point of view of users:
> >
> > There's much worth in having a very stable kernel. Many people use for
> > different reasons self-compiled ftp.kernel.org kernels.
>
> Well. We'll see. 2.6 is becoming stabler, despite the fact that we're
> adding features.
4kb stacks were added after 2.6.0 and now 4KSTACKS=y results in Oops'es
under some circumstances if using XFS.
2.6 currently still becomes stabler, but every new/changed feature bears
the risk of breaking something.
> I wouldn't be averse to releasing a 2.6.20.1 which is purely stability
> fixes against 2.6.20 if there is demand for it. Anyone who really cares
> about stability of kernel.org kernels won't be deploying 2.6.20 within a
> few weeks of its release anyway, so by the time they doodle over to
> kernel.org they'll find 2.6.20.2 or whatever.
Who will maintain the many subtrees of 2.6 this implies?
Even after 2.6.20 was already released, you might have to release a
2.6.19.5 with a few additional security fixes since according to your
advice users should continue to use 2.6.19 for a few weeks which
implies that someone will have to maintain at least the 2.6.19 tree for
at least a few weeks after the release of 2.6.20 .
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-07-22 20:19 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 14:15 [PATCH] delete devfs Greg KH
2004-07-21 14:26 ` Oliver Neukum
2004-07-21 14:35 ` Lars Marowsky-Bree
2004-07-21 14:52 ` Greg KH
2004-07-21 21:19 ` Jesse Stockall
2004-07-21 21:27 ` Greg KH
2004-07-21 21:53 ` Jesse Stockall
2004-07-21 22:05 ` Greg KH
2004-07-21 22:17 ` Jesse Stockall
2004-07-21 22:47 ` Oliver Neukum
2004-07-22 6:49 ` Greg KH
2004-07-22 9:55 ` Oliver Neukum
2004-07-22 10:08 ` Paolo Ciarrocchi
2004-07-22 16:13 ` Matt Porter
2004-07-23 19:06 ` [RFC]: CONFIG_UNSUPPORTED (was: Re: [PATCH] delete devfs) R. J. Wysocki
2004-07-23 20:04 ` Adrian Bunk
2004-07-23 21:17 ` Russell King
2004-07-23 21:22 ` R. J. Wysocki
2004-07-23 23:35 ` Sam Ravnborg
2004-07-23 22:01 ` [RFC]: CONFIG_UNSUPPORTED Stephen Wille Padnos
2004-07-22 1:08 ` [PATCH] delete devfs Grzegorz Jaśkiewicz
2004-07-22 1:48 ` Mike Snitzer
2004-07-21 22:02 ` Adrian Bunk
2004-07-21 22:07 ` Greg KH
2004-07-21 22:14 ` David Weinehall
2004-07-21 22:31 ` Brian Gerst
2004-07-21 23:11 ` New dev model (was [PATCH] delete devfs) Jonathan Corbet
2004-07-21 23:52 ` Adrian Bunk
2004-07-22 9:55 ` Andrew Morton
2004-07-22 7:04 ` Greg KH
2004-07-22 10:19 ` Andrew Morton
2004-07-22 12:55 ` Josh Boyer
2004-07-22 11:32 ` Giacomo A. Catenazzi
2004-07-22 19:12 ` Greg KH
2004-07-22 19:33 ` Adrian Bunk
2004-07-22 22:28 ` Paul Jackson
2004-07-22 23:25 ` Adrian Bunk
2004-07-23 2:22 ` Tim Wright
2004-07-23 6:31 ` Ville Herva
2004-07-23 21:04 ` Valdis.Kletnieks
2004-07-23 21:08 ` Ville Herva
2004-07-25 11:59 ` Jan Knutar
2004-07-25 18:53 ` Jesper Juhl
2004-07-23 8:16 ` szonyi calin
2004-07-23 12:21 ` Jonathan Corbet
2004-07-23 19:59 ` Adrian Bunk
2004-07-24 14:24 ` Marcelo Tosatti
2004-07-23 14:54 ` Geert Uytterhoeven
2004-07-23 15:50 ` szonyi calin
2004-07-27 22:18 ` Bill Davidsen
2004-07-28 21:25 ` Krzysztof Halasa
2004-08-02 18:48 ` Bill Davidsen
2004-08-03 22:07 ` Krzysztof Halasa
2004-07-24 16:21 ` Ragnar Hojland Espinosa
2004-07-27 22:12 ` Bill Davidsen
2004-07-28 7:24 ` Paul Jackson
2004-07-22 23:01 ` Andrew Morton
2004-07-22 20:18 ` Adrian Bunk [this message]
2004-07-22 20:28 ` Kevin Fox
2004-07-23 20:09 ` Adrian Bunk
2004-07-22 21:01 ` Martin Schlemmer
2004-07-23 0:39 ` Jason Cooper
2004-07-23 20:57 ` Timothy Miller
2004-07-25 13:30 ` Adrian Bunk
2004-07-26 1:38 ` Ben Hoskings
2004-07-26 2:12 ` Bernd Eckenfels
2004-07-28 6:25 ` Ben Hoskings
2004-07-28 21:23 ` Krzysztof Halasa
2004-08-04 21:53 ` Bernd Eckenfels
2004-07-28 21:22 ` Krzysztof Halasa
2004-07-29 12:25 ` Adrian Bunk
2004-07-22 1:33 ` [PATCH] delete devfs Mike Snitzer
2004-07-21 23:26 ` R. J. Wysocki
2004-07-21 22:11 ` Francois Romieu
2004-07-21 22:40 ` Adrian Bunk
2004-07-21 23:15 ` Francois Romieu
2004-07-22 8:23 ` sam
2004-07-22 10:24 ` Gene Heskett
2004-07-22 10:58 ` Nick Piggin
2004-07-22 21:06 ` sam
2004-07-23 0:21 ` Gene Heskett
2004-07-22 22:19 ` Paul Jakma
2004-07-22 19:22 ` Martin Schlemmer
2004-07-22 17:56 ` Deepak Saxena
2004-07-21 14:52 ` Geert Uytterhoeven
2004-07-21 14:41 ` Matthew Garrett
2004-07-21 18:25 ` Greg KH
2004-07-21 19:55 ` Matthew Garrett
2004-07-21 19:34 ` Chris Wedgwood
2004-07-21 21:13 ` Ben Collins
2004-07-21 22:20 ` Wichert Akkerman
2004-07-22 19:44 ` Martin Schlemmer
2004-07-21 15:49 ` Kasper Sandberg
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 7:45 New dev model (was [PATCH] delete devfs) Svetoslav Slavtchev
2004-07-22 10:40 ` Han Boetes
2004-07-22 13:17 Svetoslav Slavtchev
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=20040722201858.GG19329@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=corbet@lwn.net \
--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