From: Helge Hafting <helgehaf@idb.hist.no>
To: Anuradha Ratnaweera <anuradha@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.16
Date: Tue, 27 Nov 2001 10:57:29 +0100 [thread overview]
Message-ID: <3C036389.682422E6@idb.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.21.0111261003070.13400-100000@freak.distro.conectiva> <20011127083530.A13584@bee.lk> <3C02FDF4.22927E4A@mandrakesoft.com> <20011127085621.A14241@bee.lk>
Anuradha Ratnaweera wrote:
>
> On Mon, Nov 26, 2001 at 09:44:04PM -0500, Jeff Garzik wrote:
> > Anuradha Ratnaweera wrote:
> > >
> > > On Mon, Nov 26, 2001 at 10:30:08AM -0200, Marcelo Tosatti wrote:
> > > >
> > > > final:
> > > > - Fix 8139too oops (Philipp Matthias Hahn)
> > >
> > > Won't that be a good idea to keep the -final the same as the last -pre?
> >
> > No. There is absolutely no reason not to fix this oops.
>
> I wasn't refering to 8139 driver, but the kernel release policy.
A "policy" is a simplification that isn't needed.
This fix could trivially be proved not to make things worse, so
no reason at all to omit it. Policies, rules-of-thumb etc.
is for management and others without detail knowledge.
Those who know better shouldn't be limited by such rules.
And they aren't. :-)
Of course it is possible to write down a detailed policy
that even expert coders could agree to - but why bother?
You wouldn't get it into a few lines...
Helge Hafting
next prev parent reply other threads:[~2001-11-27 9:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 12:30 Linux 2.4.16 Marcelo Tosatti
2001-11-26 14:31 ` Firewire hotplug Samuel Maftoul
2001-11-26 15:58 ` William Stearns
2001-11-26 16:55 ` Linux 2.4.16 Dominik Kubla
2001-11-27 2:35 ` Anuradha Ratnaweera
2001-11-27 2:44 ` Jeff Garzik
2001-11-27 2:56 ` Anuradha Ratnaweera
2001-11-27 9:57 ` Helge Hafting [this message]
2001-11-27 7:51 ` Rik van Riel
2001-11-27 7:58 ` Anuradha Ratnaweera
2001-11-27 8:08 ` H. Peter Anvin
2001-11-27 8:26 ` Andreas Jaeger
2001-11-27 8:45 ` Anuradha Ratnaweera
2001-11-27 10:00 ` Alan Cox
2001-11-28 13:38 ` Marcelo Tosatti
2001-11-29 2:44 ` Anuradha Ratnaweera
2001-11-29 3:08 ` Rik van Riel
2001-11-29 4:09 ` Mike Fedyk
2001-11-29 12:38 ` Horst von Brand
2001-11-29 13:50 ` Rik van Riel
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=3C036389.682422E6@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=anuradha@gnu.org \
--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