Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "palves@redhat.com" <palves@redhat.com>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>
Subject: RE: [PATCH V3] Improve user experience in printing Fortran derived types.
Date: Tue, 21 Jun 2016 08:24:00 -0000	[thread overview]
Message-ID: <AC542571535E904D8E8ADAE745D60B1944610324@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <864m8nrmkt.fsf@gmail.com>

Yao,

Thanks for your prompt review!

I will add a link to the last revision when sending the new patch, sorry for that.

For the derived-type-function.exp, I am fixing the name.

Thanks again,
Fred
-----Original Message-----
From: Yao Qi [mailto:qiyaoltc@gmail.com] 
Sent: Tuesday, June 21, 2016 9:08 AM
To: Tedeschi, Walfred <walfred.tedeschi@intel.com>
Cc: palves@redhat.com; qiyaoltc@gmail.com; gdb-patches@sourceware.org
Subject: Re: [PATCH V3] Improve user experience in printing Fortran derived types.

Walfred Tedeschi <walfred.tedeschi@intel.com> writes:

Hi Walfred,
When you post V3, please give a link to V2 in your email, so that I can recall the review last time.

Patch is good to me.

> +! Ihis file is the Fortran source file for derived-type.exp.  It was

derived-type-function.exp?

--
Yao (齐尧)
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

      reply	other threads:[~2016-06-21  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  7:17 Walfred Tedeschi
2016-06-21  8:08 ` Yao Qi
2016-06-21  8:24   ` Tedeschi, Walfred [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=AC542571535E904D8E8ADAE745D60B1944610324@IRSMSX104.ger.corp.intel.com \
    --to=walfred.tedeschi@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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