From: Mark Mitchell <mark@codesourcery.com>
To: "S. Bosscher" <S.Bosscher@student.tudelft.nl>
Cc: "'gcc@gcc.gnu.org '" <gcc@gcc.gnu.org>
Subject: RE: GCC 3.3 Status
Date: Mon, 28 Apr 2003 08:14:00 -0000 [thread overview]
Message-ID: <1051509792.8310.22.camel@doubledemon.codesourcery.com> (raw)
In-Reply-To: <4195D82C2DB1D211B9910008C7C9B06F01F3732B@lr0nt3.lr.tudelft.nl>
On Tue, 2003-04-22 at 16:14, S. Bosscher wrote:
> Mark,
>
> You already have downgraded quite a few PRs, and now you're about to
> downgrade a few more. I think that for 3.3 it is the right decision (heck,
> it's got to go out now, can't wait forever), but is it your intention to
> upgrade those PRs again once 3.3 is released?
For most of them, I'm just taking the 3.3 out of the synopsis; that
pushes them into the 3.4 list. For something like "unclear error
message", I might downgrade the PR to medium priority; I'm not sure that
we'd ever hold up a release for that.
> Many PRs against 3.3 have been simply ignored, or were not recognised as
> regressions, for some time (until Wolfgang started his Great Work of
> analysing all those PRs). Most of them are still present on the trunk. And
> they _are_ regressions, even if everybody agrees that they should not hold
> up 3.3 any longer.
Yes, Wolfgang's contribution has been massive. Truly outstanding. And
yes, we need to try to fix more of these for 3.4.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next prev parent reply other threads:[~2003-04-28 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 23:55 S. Bosscher
2003-04-28 8:14 ` Mark Mitchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 10:56 GCC 3.3 status Giovanni Bajo
2005-04-20 15:21 ` Gabriel Dos Reis
2003-04-22 23:14 GCC 3.3 Status Mark Mitchell
2003-04-23 14:19 ` Jan Hubicka
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=1051509792.8310.22.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=S.Bosscher@student.tudelft.nl \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).