mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@gams.at>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Release of 2.4.21
Date: Fri, 21 Mar 2003 09:40:45 +0100	[thread overview]
Message-ID: <15812.1048236045@frodo.gams.co.at> (raw)
In-Reply-To: Your message of "Fri, 21 Mar 2003 00:13:00 GMT." <200303210013.h2L0D0jx000566@81-2-122-30.bradfords.org.uk>

John Bradford <john@grabjohn.com> wrote:
>>Why can't we just make all releases smaller and more frequent?
>
>Why do we need 2.4.x-pre at all, anyway - why can't we just test
>things in the -[a-z][a-z] trees, and _start_ with -rc1?
>
>Why can't we just do bugfixes for 2.4, and speed up 2.5 development?

Because 2.4 is used on (real) production systems - even my desktop PC
on my workplace is considered a production system - which (at least)
should run and therefore trying 2.5 is not an option (and no, no way).
And then it takes 1.5 years for the next stable kernel release which 
implies that quite new hardware (without an existing driver) cannot be
used for any production-like system.
IOW you would just loose a lot real use and testing of backported 
stuff and new hardware drivers.
And no, I don't think that someone wants that.

	Bernd

-- 
Bernd Petrovitsch                              Email : bernd@gams.at
g.a.m.s gmbh                                  Fax : +43 1 205255-900
Prinz-Eugen-Straße 8                    A-1040 Vienna/Austria/Europe
                     LUGA : http://www.luga.at



  parent reply	other threads:[~2003-03-21  8:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 19:56 Adrian Knoth
2003-03-20 20:21 ` Sebastian D.B. Krause
2003-03-20 20:34   ` Jeff Garzik
2003-03-20 20:42     ` Christoph Hellwig
2003-03-20 20:53       ` Jeff Garzik
2003-03-20 21:05         ` David Lang
2003-03-21  1:55       ` Andrew Morton
2003-03-21  0:13         ` John Bradford
2003-03-21  1:30           ` Samuel Flory
2003-03-21  9:33             ` John Bradford
2003-03-21  8:40           ` Bernd Petrovitsch [this message]
2003-03-21  9:23             ` John Bradford
2003-03-21 21:53               ` Daniel Egger
2003-03-22  8:27                 ` John Bradford
2003-03-22 14:54                   ` Daniel Egger
2003-03-21  1:01 ` Alan Cox
2003-03-21  0:04   ` David Lang
     [not found] <20030320200019$6ddc@gated-at.bofh.it>
     [not found] ` <20030320203015$4839@gated-at.bofh.it>
2003-03-20 20:43   ` Florian Weimer
2003-03-20 21:03     ` Jeff Garzik
2003-03-20 21:33       ` H. Peter Anvin
2003-03-20 22:08       ` Sebastian D.B. Krause
2003-03-21 11:06         ` Oliver Feiler
2003-03-20 22:18       ` Arador
2003-03-21  1:20       ` Chris Wright
2003-03-20 21:17 Dow, Benjamin
2003-03-21  0:57 ` Alan Cox
     [not found] <20030320205011$1378@gated-at.bofh.it>
     [not found] ` <20030320205011$0acb@gated-at.bofh.it>
     [not found]   ` <20030320205011$2c88@gated-at.bofh.it>
     [not found]     ` <20030320211011$5967@gated-at.bofh.it>
2003-03-20 21:48       ` Florian Weimer

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=15812.1048236045@frodo.gams.co.at \
    --to=bernd@gams.at \
    --cc=john@grabjohn.com \
    --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

all inboxes | Powered by JetHome®