public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Athanasius <link@miggy.org>, Bill Davidsen <davidsen@tmr.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc1
Date: Mon, 5 May 2003 21:30:26 -0700	[thread overview]
Message-ID: <20030506043026.GF8350@matchmail.com> (raw)
In-Reply-To: <20030425203017.GA16910@miggy.org>

On Fri, Apr 25, 2003 at 09:30:17PM +0100, Athanasius wrote:
> On Fri, Apr 25, 2003 at 12:17:43PM -0400, Bill Davidsen wrote:
> > I dont think this is a fix, it's a work-around. It shouldn't be
> > documnented, it should be made to work. That might mean having the kbuild
> > prevent inappropriate use, of course.
> 
>   Agreed, I more meant it needs documenting so that those people that
> hit it can apply the workaround and otherwise test the kernels.  I guess
> for now those of us that know about it will just have to keep an eye out
> for others reporting the problem then clue them in.

It's probably better this way.  If people don't know the work around, then
it will probably be reported again.  And the more it's reported with
successive versions the more corner cases will be found and fixed.

Documentation for work-arounds are meant for a proprietary world, and are
counter productive for open source.

  reply	other threads:[~2003-05-06  4:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cistron.Pine.LNX.4.53L.0304211545580.12940@freak.distro.conectiva>
     [not found] ` <E198M48-0000tC-00@ncc1701.cistron.net>
2003-04-23 15:36   ` Linux 2.4.21-rc1 Athanasius
2003-04-23 16:40     ` Athanasius
2003-04-25 16:17       ` Bill Davidsen
2003-04-25 20:30         ` Athanasius
2003-05-06  4:30           ` Mike Fedyk [this message]
2003-04-21 18:47 Marcelo Tosatti
2003-04-21 19:58 ` Stephan von Krawczynski
2003-04-21 22:49 ` Ben Greear
2003-04-21 23:24   ` Willy Tarreau
2003-04-21 23:10 ` J.A. Magallon
2003-04-22  3:00 ` Corey Minyard
2003-04-22 21:49   ` Marcelo Tosatti
2003-04-22 22:54     ` Corey Minyard
2003-04-22 13:42 ` Geert Uytterhoeven
2003-04-22 17:09 ` Rene Rebe
2003-04-22 19:15 ` Lukasz Trabinski
2003-04-22 22:59 ` J.A. Magallon
2003-04-23  8:08 ` Jerome Chantelauze
2003-04-23 15:09 ` Athanasius
2003-04-23 20:46 ` Olaf Hering
2003-04-30 21:30   ` Carl-Daniel Hailfinger
2003-04-25  3:06 ` Lucas Correia Villa Real
2003-06-07 19:35   ` Adrian Bunk
2003-06-11  4:27     ` Lucas Correia Villa Real
2003-04-25  3:13 ` Lucas Correia Villa Real
2003-04-25 14:15 ` Andreas Metzler
2003-04-25 14:27   ` Martin Josefsson
2003-04-25 14:46     ` Andreas Metzler
2003-04-25 16:19 ` Zed Pobre
2003-04-25 16:24   ` Marc-Christian Petersen
2003-05-06  2:57 ` Mike Fedyk

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=20030506043026.GF8350@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=davidsen@tmr.com \
    --cc=link@miggy.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