From: Richard Guenther <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org, java@gcc.gnu.org,
libstdc++@gcc.gnu.org
Subject: Trunk in regular stage1 again
Date: Tue, 08 Sep 2009 09:13:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.0909081112460.28140@zhemvz.fhfr.qr> (raw)
In-Reply-To: <alpine.LNX.2.00.0909031434460.28140@zhemvz.fhfr.qr>
On Thu, 3 Sep 2009, Richard Guenther wrote:
> As we've got quite some build problems on some targets and we clashed
> with VTA, free-lang-data, expand and scheduler changes it's a good
> time to slush the trunk for a short time.
>
> Thus, starting from now the trunk is in regression and documentation
> fixes only mode.
>
> Please help sorting out issues on your targets.
We're back in a reasonable state. The trunk is open under the usual
stage1 rules again.
Richard.
prev parent reply other threads:[~2009-09-08 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 12:37 Regression fixes only Richard Guenther
2009-09-08 9:13 ` Richard Guenther [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=alpine.LNX.2.00.0909081112460.28140@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=libstdc++@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).