From: Mike Fedyk <mfedyk@matchmail.com>
To: Adam McKenna <adam-dated-1018827432.0ef497@flounder.net>
Cc: David Lang <david.lang@digitalinsight.com>, linux-kernel@vger.kernel.org
Subject: Re: The latest -ac patch to the stable Linux kernels
Date: Tue, 9 Apr 2002 18:05:29 -0700 [thread overview]
Message-ID: <20020410010529.GC23513@matchmail.com> (raw)
In-Reply-To: <20020409233710.GD22300@flounder.net> <Pine.LNX.4.44.0204091646380.28293-100000@dlang.diginsite.com>
On Tue, Apr 09, 2002 at 04:47:47PM -0700, David Lang wrote:
> all the -ac kernels need to be treated as -pre
>
Exactly.
> if you watch in detail you can pick ones that are more likly to be stable
> then others, but some of them will be intentionally cutting edge.
>
Alan does have a track record of stable kernels, but his tree does have
quite a lot of experimental patches in it. He does warn about patches that
could be quite bad though (think ide and the recent suspend patches).
In fact, I'm using some -ac kernels in production after it has survived on
my workstation for a while and there haven't been any bug reports for the
stuff I use...
Also, 2.4.18 is the first time that I've seen Alan have -ac patches directly
against 2.4.xx instead of 2.4.xx-pre. Unless he says otherwise I wouldn't
expect that to happen again.
Mike
next prev parent reply other threads:[~2002-04-10 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 23:01 The latest -ac patch to the stable Linux kernels Adam McKenna
2002-04-09 23:37 ` David Ford
[not found] ` <20020409233710.GD22300@flounder.net>
2002-04-09 23:47 ` David Lang
2002-04-10 1:05 ` Mike Fedyk [this message]
2002-04-11 20:38 ` Adam McKenna
2002-04-11 20:53 ` Rik van Riel
2002-04-10 5:00 ` David Ford
2002-04-10 6:16 ` Bill Davidsen
2002-04-10 12:02 ` Denis Vlasenko
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=20020410010529.GC23513@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=adam-dated-1018827432.0ef497@flounder.net \
--cc=david.lang@digitalinsight.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.