From: Eli Zaretskii <eliz@gnu.org>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PING 2][PATCH V4 0/3] fortran: Enable arrays of structures with dynamic member types.
Date: Tue, 26 Apr 2016 13:48:00 -0000 [thread overview]
Message-ID: <83a8kg1nyt.fsf@gnu.org> (raw)
In-Reply-To: <571F5A9D.9050703@intel.com> (message from Bernhard Heckel on Tue, 26 Apr 2016 14:10:05 +0200)
> Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org, brobecker@adacore.com
> From: Bernhard Heckel <bernhard.heckel@intel.com>
> Date: Tue, 26 Apr 2016 14:10:05 +0200
>
> Reviewing NEWS is pending.
Sorry, NEWS is OK.
prev parent reply other threads:[~2016-04-26 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 6:42 [PATCH " Bernhard Heckel
2016-04-15 6:42 ` [PATCH V4 1/3] fort_dyn_array: Enable dynamic member types inside a structure Bernhard Heckel
2016-04-21 6:03 ` [PING][PATCH V4 0/3] fortran: Enable arrays of structures with dynamic member types Bernhard Heckel
2016-04-26 12:10 ` [PING 2][PATCH " Bernhard Heckel
2016-04-26 13:48 ` Eli Zaretskii [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=83a8kg1nyt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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