From: Tom Tromey <tom@tromey.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC PATCH] Introduce dwarf2_cu::get_builder
Date: Wed, 16 Jan 2019 16:38:00 -0000 [thread overview]
Message-ID: <87zhs0muby.fsf@tromey.com> (raw)
In-Reply-To: <e8c38e79-5292-85b1-4040-7a8e541faf94@redhat.com> (Keith Seitz's message of "Tue, 8 Jan 2019 11:56:00 -0800")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
[...]
Keith> The test is unchanged, I simply forgot to include them (for
Keith> $uknown reasons).
FAOD this patch is ok. It came up on irc yesterday that Keith was
waiting for an approval.
Tom
prev parent reply other threads:[~2019-01-16 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 18:57 Keith Seitz
2018-10-23 19:41 ` Sergio Durigan Junior
2018-11-06 21:34 ` Keith Seitz
2018-11-14 16:20 ` Keith Seitz
2018-11-16 13:19 ` Simon Marchi
2018-11-16 14:39 ` Keith Seitz
2018-11-30 20:30 ` Tom Tromey
2019-01-08 19:56 ` Keith Seitz
2019-01-16 16:38 ` 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=87zhs0muby.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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