From: "Tom G. Christensen" <tgc@jupiterrise.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Buildstat update for 5.1
Date: Mon, 01 Jun 2015 19:42:00 -0000 [thread overview]
Message-ID: <20150601194248.GD7781@odin.tgcnet> (raw)
In-Reply-To: <alpine.LSU.2.20.1505291605170.2921@tuna.site>
On Fri, May 29, 2015 at 04:05:57PM +0200, Gerald Pfeifer wrote:
> Did we get more updates for GCC 5.1 in the meantime?
>
Yes and I have just posted a new set of patches.
-tgc
next prev parent reply other threads:[~2015-06-01 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 15:28 Tom G. Christensen
2015-05-29 14:14 ` Gerald Pfeifer
2015-06-01 19:42 ` Tom G. Christensen [this message]
2015-06-01 19:41 Tom G. Christensen
2015-06-02 13:30 ` Gerald Pfeifer
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=20150601194248.GD7781@odin.tgcnet \
--to=tgc@jupiterrise.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).