From: Stuart Young <sgy@amc.com.au>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Anuradha Ratnaweera <anuradha@gnu.org>, bert hubert <ahu@ds9a.nl>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: linux-2.4.13..
Date: Fri, 26 Oct 2001 15:44:33 +1000 [thread overview]
Message-ID: <5.1.0.14.0.20011026151926.00a23d60@mail.amc.localnet> (raw)
In-Reply-To: <20011026081728.A14607@bee.lk>
In-Reply-To: <20011024114026.A14078@outpost.ds9a.nl> <Pine.LNX.4.33.0110232249090.1185-100000@penguin.transmeta.com> <20011024114026.A14078@outpost.ds9a.nl>
At 08:17 AM 26/10/01 +0600, Anuradha Ratnaweera wrote:
>IMHO _nothing_ should be done for the final. A better alternative is to
>name a stable pre kernel as a final without changes. In the current
>scenario, a final kernel release is one which is _not_ tested.
My "personal" opinion is that final's are for Documentation updates,
correction of spelling errors in comments (not code, which needs testing),
and *possibly* trivial updates to data files (eg: like
linux/drivers/pci/pci.ids).
There have been a number of 2.4 issues in finals. Not all of them as
staggering as 2.4.11, but things like the driver issues with the sblive
(emu10k1) joystick stuff comes to mind, which was a 'final' addition.
Admittedly it's not a hugely critical system, but it was fairly visible.
What would also be nice is a list of actual changed files for each patch
mentioned in the ChangeLog, which if there is a problem between 2 revisions
of a kernel (wether they're pre's of the same major kernel, or different
major kernels), could really help pinpoint some problems a hell of a lot
faster. Doesn't have to be in the ChangeLog, but it'd nice to have about
(especially for those that don't keep every version of the kernel on disk).
Then again, opinions are like..... *grin*
AMC Enterprises P/L - Stuart Young
First Floor - Network and Systems Admin
3 Chesterville Rd - sgy@amc.com.au
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755
next prev parent reply other threads:[~2001-10-26 5:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 5:52 linux-2.4.13 Linus Torvalds
2001-10-24 7:39 ` linux-2.4.13 christophe barbe
2001-10-24 8:08 ` linux-2.4.13 Florian Weimer
2001-10-24 8:56 ` linux-2.4.13 Tim Nicholas
2001-10-25 10:29 ` linux-2.4.13 André Dahlqvist
2001-10-24 9:40 ` linux-2.4.13 bert hubert
2001-10-24 16:51 ` linux-2.4.13 Linus Torvalds
2001-10-24 17:05 ` linux-2.4.13 high SWAP Andre Margis
2001-10-24 17:42 ` Andre Margis
2001-10-24 16:44 ` Marcelo Tosatti
2001-10-24 18:20 ` Andre Margis
2001-10-24 17:10 ` Marcelo Tosatti
2001-10-24 18:37 ` Andre Margis
2001-10-24 19:11 ` Linus Torvalds
2001-10-24 21:03 ` Lukasz Trabinski
2001-10-24 21:48 ` toon
2001-10-24 22:08 ` David S. Miller
2001-10-25 13:23 ` Christoph Rohland
2001-10-26 2:17 ` linux-2.4.13 Anuradha Ratnaweera
2001-10-24 11:16 ` linux-2.4.13 Andy Pevy
2001-10-24 10:56 ` linux-2.4.13 Francois Romieu
2001-10-24 14:48 ` linux-2.4.13 Jan Rekorajski
2001-10-26 5:44 ` Stuart Young [this message]
2001-10-24 14:35 linux-2.4.13 Markus Döhr
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=5.1.0.14.0.20011026151926.00a23d60@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=ahu@ds9a.nl \
--cc=anuradha@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®