From: Nicholas Knight <tegeran@home.com>
To: David Ford <david@blue-labs.org>, PinkFreud <pf-kernel@mirkwood.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Are we going too fast?
Date: Mon, 13 Aug 2001 21:19:30 -0700 [thread overview]
Message-ID: <01081321193002.00204@c779218-a> (raw)
In-Reply-To: <Pine.LNX.4.20.0108131656470.1037-100000@eriador.mirkwood.net> <3B788BDC.100@blue-labs.org>
In-Reply-To: <3B788BDC.100@blue-labs.org>
On Monday 13 August 2001 07:24 pm, David Ford wrote:
> PinkFreud wrote:
> >I wasn't aware VIA nor Matrox were broken. I've seen someone else
> > mention in this thread that perhaps some old HOWTOs on hardware need
> > to be maintained again - I think I agree with that.
>
> VIA comes up as a bloody thorn quite often it seems. I have a VIA 586B
> system and it seems to work decently but I think I'm just lucky
> considering the large number of broken VIA chipset complaints.
>
> >Perhaps series name should be changed from 'stable' to something else
> > - 'release'?
>
> Erm...they are called release. 2.<even> is a release kernel and
> 2.<odd> is a development kernel. Some people (myself included) fight
> the impression given by a lot of people of stable/unstable naming.
> Typically called slashdotters...</humor>
If this is truely the case, I'd suggest that kernel.org be modified, as
it refers to them as *stable*
as of 9:18PM PDT, direct copy & paste from kernel.org page:
The latest stable version of the Linux kernel is: 2.4.8 2001-08-11 04:13
UTC Changelog
The latest prepatch (alpha) version appears to be: 2.4.9-pre3 2001-08-13
23:56 UTC Changelog
next prev parent reply other threads:[~2001-08-14 4:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 21:07 Are we going too fast? 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 [this message]
2001-08-14 12:49 ` Alan Cox
2001-08-14 22:27 ` Paul G. Allen
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 21:42 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 19:47 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
[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-13 10:09 ` Chris Wilson
2001-08-13 11:09 ` szonyi calin
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 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=01081321193002.00204@c779218-a \
--to=tegeran@home.com \
--cc=david@blue-labs.org \
--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