From: Mark Mitchell <mark@codesourcery.com>
To: Nathan Sidwell <nathan@codesourcery.com>,
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: Bug tracking / Release Quality Assurance
Date: Tue, 08 Oct 2002 12:38:00 -0000 [thread overview]
Message-ID: <1750000.1034084486@localhost> (raw)
In-Reply-To: <3DA1B4F1.9070304@codesourcery.com>
--On Monday, October 07, 2002 05:23:13 PM +0100 Nathan Sidwell
<nathan@codesourcery.com> wrote:
> Gerald Pfeifer wrote:
>> Checking the GNATS database which currently shows 62 high priority
>> problems, there are some points I'd like to raise:
>>
>> 1. I believe we should not ship GCC 3.2.1 (or branch 3.3.) until this
>> bug count has been significantly reduce.
> I concur.
Me too.
I will be making a concerted effort to fix the C++ bugs.
Please help as you are best able.
If you are laboring along on a branch, please take the time to work on
fixing a few bugs. If we all fix three or four, we'll be done in
no time. Your branch isn't going to be released until we are done with
this release, so your work is going to see the light of day much sooner
if you pitch in now.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-10-08 18:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 9:38 Gerald Pfeifer
2002-10-07 9:42 ` David S. Miller
2002-10-07 10:26 ` Jakub Jelinek
2002-10-07 9:50 ` Nathan Sidwell
2002-10-08 12:38 ` Mark Mitchell [this message]
2002-10-08 16:07 ` Pop Sébastian
2002-12-07 6:53 ` Gerald Pfeifer
2002-12-08 19:16 ` Mark Mitchell
2002-12-09 10:06 ` PATCH for " Gerald Pfeifer
2002-10-08 0:43 ` Gabriel Dos Reis
2002-10-08 7:31 Roger Sayle
2002-10-08 8:53 ` Neil Booth
2002-10-08 8:59 ` Roger Sayle
2002-10-10 8:01 Nathanael Nerode
2002-12-09 10:14 Volker Reichelt
2002-12-09 10:42 ` Mark Mitchell
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=1750000.1034084486@localhost \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).