From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH v2] Explicitly use language_c when evaluating a SDT probe argument
Date: Tue, 14 Oct 2014 21:14:00 -0000 [thread overview]
Message-ID: <87k342pd5w.fsf@redhat.com> (raw)
In-Reply-To: <20141014210757.GA8713@adacore.com> (Joel Brobecker's message of "Tue, 14 Oct 2014 14:07:57 -0700")
On Tuesday, October 14 2014, Joel Brobecker wrote:
> Thanks, Pedro. And since you took the time to fix the issue on
> the SDT side, I took the time to push the ada-lang.c patch which
> I wrote on our side :-).
My pleasure! (though I imagine you meant "Sergio" :-P.)
> https://www.sourceware.org/ml/gdb-patches/2014-10/msg00371.html
This is what I call a two-factor fix :-).
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2014-10-14 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 18:40 Sergio Durigan Junior
2014-10-14 18:35 ` Sergio Durigan Junior
2014-10-14 21:08 ` Joel Brobecker
2014-10-14 21:14 ` Sergio Durigan Junior [this message]
2014-10-15 13:32 ` Pedro Alves
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=87k342pd5w.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.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