From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>,
Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/2] gdb: add type::code / type::set_code
Date: Tue, 12 May 2020 15:04:33 -0600 [thread overview]
Message-ID: <87k11gdfvi.fsf@tromey.com> (raw)
In-Reply-To: <554f216e-107c-af83-7e9f-19a3e449b27e@simark.ca> (Simon Marchi's message of "Tue, 12 May 2020 16:38:00 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> That crossed my mind too, but did not try it, to go one step at
Simon> the time. I'll try it eventually.
Yeah, makes sense.
BTW I did not see patch 2/2.
Tom
next prev parent reply other threads:[~2020-05-12 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 23:48 Simon Marchi
2020-05-12 20:35 ` Tom Tromey
2020-05-12 20:38 ` Simon Marchi
2020-05-12 21:04 ` Tom Tromey [this message]
2020-05-12 21:15 ` Simon Marchi
2020-05-12 21:23 ` [PATCH 2/2] gdb: remove TYPE_CODE macro Simon Marchi
2020-05-13 19:24 ` Tom Tromey
2020-05-14 17:59 ` Simon Marchi
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=87k11gdfvi.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).