From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: GNU Cauldron
Date: Tue, 30 Aug 2016 22:06:00 -0000 [thread overview]
Message-ID: <72640866-3eec-8bcc-7cba-b42a28c98332@redhat.com> (raw)
In-Reply-To: <CAH=s-POVQHQ+Ewfb39rmde=Jy1kKmB0L6bUEYcZARESZwZtcDA@mail.gmail.com>
On 07/20/2016 05:10 PM, Yao Qi wrote:
> Does anyone go to Cauldron?
Yep, I'm going.
> Do we need a GDB BoF?
Yes, I think it's a good opportunity to put people in the
same room and discuss things.
There's was no GDB BoF listed yet [1], and time was running
out, so I've filed for one. It's been accepted and is listed now.
Everyone feel free to come over and bring discussion topics. :-)
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.
[1] - https://gcc.gnu.org/wiki/cauldron2016
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-08-30 22:06 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 [this message]
2016-09-07 8:15 ` Yao Qi
2016-09-07 10:41 ` Pedro Alves
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=72640866-3eec-8bcc-7cba-b42a28c98332@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