From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC-3.3.4 status report
Date: Thu, 29 Apr 2004 02:20:00 -0000 [thread overview]
Message-ID: <m3hdv34xzm.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <200404271202.i3RC2nYU010034@relay.rwth-aachen.de>
Volker Reichelt <reichelt@igpm.rwth-aachen.de> writes:
| On 27 Apr, Gabriel Dos Reis wrote:
| > Volker Reichelt <reichelt@igpm.rwth-aachen.de> writes:
| >
| > | Hi Gaby,
| > |
| > | you wrote:
| > |
| > | > There are 25 open PRs targetted for 3.3.4. Of course, I don't
| > | > expect all of them to be fixed before the release. The most serious
| > | > PRs are the regressions:
| > | >
| > | > optimization/13653
| > |
| > | On the other hand you closed PR 11841 today which is probably the same
| > | bug as PR 13653, but it sports a short testcase (whereas it seems to be
| >
| > The audit trail of 11841 seems very confused to the point where it is
| > not obvious that it is the same.
|
| Good point. I just added a (hopefully less confusing) summary to the
| audit trail, reopened the PR and marked PR 13653 as dependent on it.
Thanks!
-- Gaby
next prev parent reply other threads:[~2004-04-28 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 14:09 Volker Reichelt
2004-04-29 2:20 ` Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-28 13:33 GCC-3.3.4 Status Report Gabriel Dos Reis
2004-05-16 23:08 GCC-3.3.4 status report Gabriel Dos Reis
2004-05-17 1:14 ` Giovanni Bajo
2004-05-17 5:19 ` Gabriel Dos Reis
2004-05-18 15:42 ` Gabriel Dos Reis
2004-04-27 12:02 Volker Reichelt
2004-04-27 12:10 ` Gabriel Dos Reis
2004-04-27 10:15 Gabriel Dos Reis
2004-04-27 10:43 ` Giovanni Bajo
2004-04-27 11:24 ` Gabriel Dos Reis
2004-04-27 22:07 ` Matthias Klose
2004-04-29 3:05 ` Gabriel Dos Reis
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=m3hdv34xzm.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=reichelt@igpm.rwth-aachen.de \
/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).