From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCHv2 0/4] Fortran info types, info modules, info module ...
Date: Thu, 10 Oct 2019 15:59:00 -0000 [thread overview]
Message-ID: <87tv8g7fry.fsf@tromey.com> (raw)
In-Reply-To: <cover.1570101531.git.andrew.burgess@embecosm.com> (Andrew Burgess's message of "Thu, 3 Oct 2019 12:29:13 +0100")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> This is a new version of the series I originally posted here:
Andrew> https://sourceware.org/ml/gdb-patches/2019-07/msg00608.html
I read through these. Aside from some tiny nits for patch #4,
everything looked good to me.
Tom
prev parent reply other threads:[~2019-10-10 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 11:29 Andrew Burgess
2019-10-03 11:29 ` [PATCHv2 2/4] gdb/fortran: Add test for module variables in 'info variables' output Andrew Burgess
2019-10-03 11:29 ` [PATCHv2 1/4] gdb/testsuite: Allow cc-with-tweaks board file to be used with Fortran Andrew Burgess
2019-10-03 11:29 ` [PATCHv2 3/4] gdb/fortran: Add new 'info modules' command Andrew Burgess
2019-10-03 16:12 ` Eli Zaretskii
2019-10-03 11:29 ` [PATCHv2 4/4] gdb: Add new commands to list module variables and functions Andrew Burgess
2019-10-03 16:16 ` Eli Zaretskii
2019-10-10 15:58 ` Tom Tromey
2019-11-22 12:44 ` Tom de Vries
2019-11-27 21:29 ` Andrew Burgess
2019-11-28 9:21 ` Tom de Vries
2019-11-28 12:18 ` Andrew Burgess
2019-10-10 15:59 ` Tom Tromey [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=87tv8g7fry.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.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