From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 make allyesconfig - errors and warnings
Date: Sun, 4 Aug 2002 20:52:16 +0200 [thread overview]
Message-ID: <20020804185216.GA23894@louise.pinerecords.com> (raw)
In-Reply-To: <1028469633.14195.19.camel@irongate.swansea.linux.org.uk>
> On Sun, 2002-08-04 at 11:02, Tomas Szepe wrote:
> > Just an idea - wouldn't it be useful to have dedicated errata pages
> > for recent stable kernels where important patches (such as the 2.4.18
> > personality fix, 2.4.18 samba oops fix or the upcoming 2.4.19 ide
> > updates) would be published? Finding a link to these in the kernel FAQ,
> > people would just patch their kernels instead of posting to lkml, which
> > could cut on the amount of duplicate bugreports significantly plus folks
> > wouldn't have to wait 6 months+ for an official update to get rid of an
> > oops.
>
> I did that for some of the 2.2 trees. I can keep an errata page on
> linux.org.uk for the 2.4.19 tree as well if people want.
That would certainly be appreciated.
> Right now the errata would be pretty small so its easy to deal with.
Something as simple as the squid fixes page would do just fine I reckon:
http://www.squid-cache.org/Versions/v2/2.4/bugs/
T.
next prev parent reply other threads:[~2002-08-04 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 9:51 2.4.19 make allyesconfig - errors and warnings Keith Owens
2002-08-04 10:02 ` Tomas Szepe
2002-08-04 14:00 ` Alan Cox
2002-08-04 18:52 ` Tomas Szepe [this message]
2002-08-04 10:09 ` J.A. Magallon
2002-08-05 13:59 ` David Woodhouse
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=20020804185216.GA23894@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--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