From: Jeff Law <law@redhat.com>
To: msebor@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gfortran.dg/pr32627.f03 prints nul byte
Date: Fri, 17 Apr 2015 19:29:00 -0000 [thread overview]
Message-ID: <55315F2C.8050800@redhat.com> (raw)
In-Reply-To: <5531482A.2040006@redhat.com>
On 04/17/2015 11:51 AM, msebor@redhat.com wrote:
> Ping. Is this patch okay for trunk?
Yes, both are OK for the trunk.
Sorry for the delay, we're really just getting started working through
stuff that was queued up for stage1.
jeff
prev parent reply other threads:[~2015-04-17 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 18:54 Martin Sebor
2015-04-09 21:16 ` Martin Sebor
2015-04-17 17:51 ` msebor
2015-04-17 19:29 ` Jeff Law [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=55315F2C.8050800@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@redhat.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).