From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: gcc@gcc.gnu.org
Subject: Please replace/augment buildstat entry
Date: Sat, 06 Aug 2011 00:51:00 -0000 [thread overview]
Message-ID: <1312591852.71521.YahooMailClassic@web29512.mail.ird.yahoo.com> (raw)
Please replace or augment the
alphaev68-dec-osf5.1a Test results: 4.4.6,
in
http://gcc.gnu.org/gcc-4.4/buildstat.html
from
http://gcc.gnu.org/ml/gcc-testresults/2011-05/msg00074.html
to
http://gcc.gnu.org/ml/gcc-testresults/2011-08/msg00586.html
The reason is explained at the top of the summary:
"This replaces my previous entry on 4.4.6 three months ago ...differs only from that earlier submission by the libgomp section ..."
reply other threads:[~2011-08-06 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1312591852.71521.YahooMailClassic@web29512.mail.ird.yahoo.com \
--to=htl10@users.sourceforge.net \
--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).