From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, bauerman@br.ibm.com, gdb@sourceware.org
Subject: Re: GDB BoF at the 2009 GCC Summit
Date: Sat, 13 Jun 2009 07:33:00 -0000 [thread overview]
Message-ID: <daef60380906130033u66cf08c1h40f150f67b9222b1@mail.gmail.com> (raw)
In-Reply-To: <E1MFJ35-0006Zo-DR@fencepost.gnu.org>
On Sat, Jun 13, 2009 at 10:32, Eli Zaretskii<eliz@gnu.org> wrote:
>> Date: Fri, 12 Jun 2009 11:10:27 +0800
>> From: Hui Zhu <teawater@gmail.com>
>> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>, gdb@sourceware.org
>>
>> I will try to there 2010. Wish I can get a sponsor for it. :)
>
> Or closer to where I live most of the year. ;-)
>
This idea is better. :)
prev parent reply other threads:[~2009-06-13 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 15:54 Joel Brobecker
2009-06-10 16:32 ` Thiago Jung Bauermann
2009-06-11 1:05 ` Hui Zhu
2009-06-11 14:04 ` Joel Brobecker
2009-06-12 3:10 ` Hui Zhu
2009-06-13 2:33 ` Eli Zaretskii
2009-06-13 7:33 ` Hui Zhu [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=daef60380906130033u66cf08c1h40f150f67b9222b1@mail.gmail.com \
--to=teawater@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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