From: Kevin Pouget <kevin.pouget@gmail.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb@sourceware.org, dnovillo@google.com
Subject: Re: GDB Talks at the GNU Cauldron
Date: Wed, 08 Feb 2012 21:03:00 -0000 [thread overview]
Message-ID: <CAPftXUK8_yPV03p8TB8tX=X_dqcL_ov+-YeE-rBTf1sY05NCLg@mail.gmail.com> (raw)
In-Reply-To: <4F32DAC8.8020408@redhat.com>
On Wed, Feb 8, 2012 at 9:27 PM, Phil Muldoon <pmuldoon@redhat.com> wrote:
>
> According to the organizers there are three to four talks at the Cauldron. Something that Diego mentioned was the need to coordinate talks. So, who has submitted abstracts, and what are their titles? It would be good to plan for this.
>
> Cheers,
>
> Phil
Hello,
as I mentioned in http://sourceware.org/ml/gdb/2012-02/msg00003.html,
I submitted an abstract entitled "Supporting Parallel Component
Debugging Using the GDB Python Interface" for a presentation
Let me know if you need further detail for the planning
Cordially,
Kevin
next prev parent reply other threads:[~2012-02-08 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 20:28 Phil Muldoon
2012-02-08 21:03 ` Kevin Pouget [this message]
2012-02-08 22:39 ` Stan Shebs
2012-02-09 8:18 ` Joachim Protze
2012-02-09 14:03 ` Jan Kratochvil
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='CAPftXUK8_yPV03p8TB8tX=X_dqcL_ov+-YeE-rBTf1sY05NCLg@mail.gmail.com' \
--to=kevin.pouget@gmail.com \
--cc=dnovillo@google.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@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