linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Per Jessen" <per@computer.org>
To: "Helge Hafting" <helgehaf@idb.hist.no>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"PinkFreud" <pf-kernel@mirkwood.net>
Subject: Re: Are we going too fast?
Date: Tue, 14 Aug 2001 21:47:53 +0200	[thread overview]
Message-ID: <3B790EE100026F51@mta1n.bluewin.ch> (raw)

On Tue, 14 Aug 2001 09:57:29 +0200, Helge Hafting wrote:

>PinkFreud wrote:
>[...]
>
>> > Matter of opinion. I would say that Linux-2.4 has been way long to come
>> > and wasn't quite ready for stable status. There are numerous other O/Ses
>> 
>> That's what I've been attempting to say, as well.  It seems to have been
>> released too quickly - minimal testing, too many bugs.
>
>The testing isn't minimal - it is merely ongoing.  Users don't
>pay for the kernel, so they are part of the testing team.
>
>If you use anything but a distribution kernel, keep previous
>kernels around when you upgrade.  If the new one fails, report
>it here and go back to the previous one.  The only way to get wide
>testing is when enough people do this.

Very true, although I get the feeling that the 2.2. series was far more
'stable' than the current 2.4 series. Just a feeling, but .... 
What you're saying seems to apply more to a 2.<odd> kernel series, IMHO ?

I haven't done this myself, but perhaps we ought to look at the frequency
of new 2.4 releases compared to new 2.2 releases. Shouldn't their frequency
be roughly equal ? ie. the speed with which we're seeing new 2.4 releases 
should be - roughly - that of which we saw new 2.2 kernels emerging ?

comments ?



regards,
Per Jessen, Zurich
http://www.enidan.com - home of the J1 serial console.

Windows 2001: "I'm sorry Dave ...  I'm afraid I can't do that."



             reply	other threads:[~2001-08-14 19:39 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 19:47 Per Jessen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-16 21:42 Are we going too fast? PinkFreud
2001-08-15 20:13 Roy Murphy
2001-08-14 20:20 Per Jessen
2001-08-14 20:07 Per Jessen
2001-08-14 16:32 PinkFreud
2001-08-14 16:25 PinkFreud
2001-08-13 21:44 PinkFreud
2001-08-14  0:04 ` PinkFreud
2001-08-14  7:24   ` Francois Romieu
2001-08-15 23:24   ` Dr. Kelsey Hudson
2001-08-13 21:36 PinkFreud
2001-08-14  7:57 ` Helge Hafting
2001-08-13 21:07 PinkFreud
2001-08-13 21:20 ` Alan Cox
2001-08-13 21:41   ` Rog�rio Brito
2001-08-14  0:56   ` Ben Ford
2001-08-14  7:34   ` Peter Wächtler
2001-08-14  2:24 ` David Ford
2001-08-14  4:19   ` Nicholas Knight
2001-08-14 12:49     ` Alan Cox
2001-08-14 22:27       ` Paul G. Allen
     [not found] <no.id>
2001-08-13 20:24 ` Alan Cox
2001-08-13 21:06   ` Anthony Barbachan
2001-08-14 20:47 ` Alan Cox
2001-08-15  0:07   ` PinkFreud
     [not found] <fa.l9dq0tv.7gqnhh@ifi.uio.no>
     [not found] ` <fa.g70as7v.1722ipv@ifi.uio.no>
2001-08-13 19:14   ` John Weber
2001-08-13 18:53 Petr Vandrovec
2001-08-13 18:46 Per Jessen
2001-08-14 13:58 ` Andrew Scott
2001-08-14 19:54 ` David Ford
2001-08-13 17:53 PinkFreud
2001-08-13 20:27 ` Gérard Roudier
2001-08-13  7:43 PinkFreud
2001-08-13  8:52 ` Brian
2001-08-13  8:55 ` Francois Romieu
2001-08-14  4:21   ` Pete Toscano
2001-08-14 12:48     ` Alan Cox
2001-08-14 22:30       ` Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29   ` Justin Guyett
2001-08-13 12:56     ` Andrzej Krzysztofowicz
2001-08-13 16:54     ` Gérard Roudier
2001-08-13 10:09 ` Chris Wilson
2001-08-13 11:09   ` szonyi calin
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51   ` Anders Larsen
2001-08-14 20:29     ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov
2001-08-13 17:16 ` Stephen Satchell

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=3B790EE100026F51@mta1n.bluewin.ch \
    --to=per@computer.org \
    --cc=helgehaf@idb.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pf-kernel@mirkwood.net \
    /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;
as well as URLs for NNTP newsgroup(s).