From: Paul Larson <plars@linuxtestproject.org>
To: Rik van Riel <riel@imladris.surriel.com>
Cc: Paul Larson <plars@linuxtestproject.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] 2.5 kernel errata list
Date: Fri, 21 Feb 2003 12:19:50 -0600 [thread overview]
Message-ID: <3E566DC6.9040706@linuxtestproject.org> (raw)
In-Reply-To: Pine.LNX.4.50L.0302192230340.2329-100000@imladris.surriel.com
Sorry for the late reply, I'm down with the flu atm.
Rik van Riel wrote:
>
>How is this different from the 2.5 bugzilla database ?
>
The bugzilla database tracks problems, whether they are fixed or not.
The errata list aims to be a quick (hopefully short) list of known
fixes to problems. Bugzilla also tracks all types of problems where the
errata list will usually only contain fixes to major, blocking problems.
Basically I'm trying to keep a list that will help people quickly find
the diffs against releases that will help them get up and running enough
to test with.
Thanks,
Paul Larson
prev parent reply other threads:[~2003-02-21 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 19:13 [ANNOUNCE] 2.5 kernel errata list Paul Larson
2003-02-20 1:31 ` Rik van Riel
2003-02-21 18:19 ` Paul Larson [this message]
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=3E566DC6.9040706@linuxtestproject.org \
--to=plars@linuxtestproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@imladris.surriel.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