From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: GNU Cauldron
Date: Wed, 07 Sep 2016 10:41:00 -0000 [thread overview]
Message-ID: <26ad12ea-64be-073e-2fb4-f28041012501@redhat.com> (raw)
In-Reply-To: <CAH=s-PN3Cca2M9jxVjCOqTNamBB3O=0eAX_dD6hiHg7UeN-OTg@mail.gmail.com>
On 09/07/2016 09:15 AM, Yao Qi wrote:
> On Tue, Aug 30, 2016 at 11:06 PM, Pedro Alves <palves@redhat.com> wrote:
>> I'm also doing a talk on status of some of the ongoing gdb
>> projects, at least those that I'm more familiar with.
>> See talks list at [1] for more info.
>>
>
> If you don't use up the time, can I have 5-10 minutes to talk about
> two or three GDB projects I am working on?
OK, let's try to squeeze it in. Last time I did a presentation
like this, I ran out of time and had to be told to shut up and
leave :-P :-)
The GDB BoF is right after my talk in the same room, so if we
end up overflowing, it doesn't look like it'll be a real
problem.
Please let me know which projects those are.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-09-07 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 16:11 Yao Qi
2016-08-30 22:06 ` Pedro Alves
2016-09-07 8:15 ` Yao Qi
2016-09-07 10:41 ` Pedro Alves [this message]
2016-09-07 11:18 ` Yao Qi
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=26ad12ea-64be-073e-2fb4-f28041012501@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.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