From: Gerald Pfeifer <gerald@pfeifer.com>
To: Dennis Clarke <blastwave@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Snapshot announcements (was: gcc-4.4-20080725 is now available)
Date: Mon, 23 Aug 2010 20:55:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1008232059300.17560@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <alpine.LNX.2.00.1008142322490.10053@acrux.dbai.tuwien.ac.at>
On Sat, 14 Aug 2010, Gerald Pfeifer wrote:
> This is an excellent idea. I just implemented a change to that
> effect and today's snapshot for GCC 4.6 has this:
>
> http://gcc.gnu.org/ml/gcc/2010-08/msg00232.html
>
> I am not really satisfied about how this looks yet and will tweak
> this a bit over time.
Now also with SHA1 hashes and slightly adjusted, cf
http://gcc.gnu.org/ml/gcc/2010-08/msg00317.html
Any comments, suggestions, hate mail, let me know.
Gerald
prev parent reply other threads:[~2010-08-23 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 0:31 gcc-4.4-20080725 is now available gccadmin
2008-07-26 0:51 ` Dennis Clarke
2010-08-15 16:07 ` Gerald Pfeifer
2010-08-23 20:55 ` Gerald Pfeifer [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.1008232059300.17560@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=blastwave@gmail.com \
--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).