From: Alexander Valys <avalys@optonline.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel QA
Date: Tue, 27 Mar 2001 17:09:19 -0500 [thread overview]
Message-ID: <01032717091900.00406@athena> (raw)
In-Reply-To: <20010327085142.A982@bessie.dyndns.org>
In-Reply-To: <Pine.LNX.4.21.0103270229310.8261-100000@imladris.rielhome.conectiva> <3AC04BAC.C21E302@konerding.com> <20010327085142.A982@bessie.dyndns.org>
On Tuesday 27 March 2001 08:51, James Lewis Nance wrote:
> Instead I think we need to encourage people who want to use Linux,
> rather than develop it, to use kernels from a distribution.
I hope that's not the opinion of all the kernel developers - where does that
leave distributions like slackware, debian, and the rest that don't have the
time or resources to modify the kernel themselves? Every kernel release that
is meant to keep developers "in sync", as you say, should be a 2.4.x-prex
release, and the stable releases should actually be stable. If this means
slowing the release schedule, so be it. You are proposing to release
unfinished, buggy and unstable code and let the distributions pick up your
slack. It sounds like something Microsoft would do.
next prev parent reply other threads:[~2001-03-27 22:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 1:56 "mount -o loop" lockup issue David E. Weekly
2001-03-27 3:31 ` Jason Madden
2001-03-27 3:50 ` David Konerding
2001-03-27 4:19 ` Alan Cox
2001-03-27 8:32 ` David Konerding
2001-03-27 13:24 ` Mohammad A. Haque
2001-03-27 18:51 ` J Sloan
2001-03-27 19:33 ` Alexander Viro
2001-03-27 5:30 ` Rik van Riel
2001-03-27 8:13 ` David Konerding
2001-03-27 12:31 ` Rik van Riel
2001-03-27 13:51 ` Kernel QA James Lewis Nance
2001-03-27 18:02 ` Shawn Starr
2001-03-27 22:09 ` Alexander Valys [this message]
2001-03-27 16:25 ` "mount -o loop" lockup issue Alan Cox
2001-03-27 3:50 ` Mohammad A. Haque
2001-03-27 3:59 ` William Stearns
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=01032717091900.00406@athena \
--to=avalys@optonline.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