From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [users/palves/catch_exceptions] [PATCH] zap catch_exceptions (Re: [RFA] Change exceptions.h functions to use gdb::function_view)
Date: Thu, 28 Sep 2017 19:53:00 -0000 [thread overview]
Message-ID: <87fub6y50i.fsf@pokyo> (raw)
In-Reply-To: <a2bc964f-7ca3-d681-a059-c577d2528afc@redhat.com> (Pedro Alves's message of "Thu, 28 Sep 2017 10:13:31 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Sorry about that. :-/ I only did it because I thought you wouldn't
Pedro> be able to...
Totally understandable and no big deal. FWIW this patch was actually
preparation for a constification patch that is still waiting here to be
submitted.
Tom
prev parent reply other threads:[~2017-09-28 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 16:53 [RFA] Change exceptions.h functions to use gdb::function_view Tom Tromey
2017-09-27 19:43 ` Pedro Alves
2017-09-27 20:26 ` Tom Tromey
2017-09-27 22:37 ` Pedro Alves
2017-09-28 0:02 ` [users/palves/catch_exceptions] [PATCH] zap catch_exceptions (Re: [RFA] Change exceptions.h functions to use gdb::function_view) Pedro Alves
2017-09-28 2:04 ` Tom Tromey
2017-09-28 9:13 ` Pedro Alves
2017-09-28 19:53 ` 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=87fub6y50i.fsf@pokyo \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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