From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Fix gdb.go/methods.exp
Date: Fri, 21 Feb 2020 18:36:00 -0000 [thread overview]
Message-ID: <877e0f7poe.fsf@tromey.com> (raw)
In-Reply-To: <2d3be3b3-fc78-1fbf-7952-64d3962c14bc@suse.de> (Tom de Vries's message of "Fri, 21 Feb 2020 17:17:02 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> I managed using maintenance print symbols.
Tom> OK for trunk like this?
Yes, thank you.
Tom
next prev parent reply other threads:[~2020-02-21 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:02 Tom de Vries
2020-02-21 14:54 ` Tom Tromey
2020-02-21 16:17 ` Tom de Vries
2020-02-21 18:36 ` Tom Tromey [this message]
2020-02-25 7:23 ` Tom de Vries
2020-02-25 7:24 ` Tom de Vries
2020-02-25 13:07 ` Tom Tromey
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=877e0f7poe.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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