From: Hui Zhu <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: GDB 7.6 branch status...
Date: Sun, 10 Mar 2013 05:04:00 -0000 [thread overview]
Message-ID: <CANFwon1T=LuCQT2s+z8ycfKroLFKq4g+nEuwq2Br_NHsftXtPg@mail.gmail.com> (raw)
In-Reply-To: <20130226031907.GA5727@adacore.com>
Hi Joel,
I just post 3 patches in:
http://sourceware.org/ml/gdb-patches/2013-03/msg00419.html
http://sourceware.org/ml/gdb-patches/2013-03/msg00421.html
All of them are bug fix patches. Suggest we fixed these issues before
7.6 release.
Thanks,
Hui
On Tue, Feb 26, 2013 at 11:19 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Just FYI, I'm going to be away the rest of the week.
>> If something ends up blocked because of me, I won't be able
>> to get to it until next week the earliest.
>> I intended to review a few patches and threads more this
>> week, but well, time flies... Apologies to whoever may
>> be affected.
>
> That will not be a problem at all. We are waiting for the btrace patch
> series to get in and so we probably have another 2 weeks before we try
> again. And we'll wait some more if there is something else we'd really
> like to be in.
>
> --
> Joel
next prev parent reply other threads:[~2013-03-10 5:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 22:42 Joel Brobecker
2013-02-19 12:20 ` Marcus Shawcroft
2013-02-19 15:27 ` Jan Kratochvil
2013-02-19 16:00 ` Metzger, Markus T
2013-02-19 16:14 ` Joel Brobecker
2013-02-19 17:11 ` Metzger, Markus T
2013-02-19 20:34 ` Joel Brobecker
2013-03-11 9:28 ` Metzger, Markus T
2013-03-11 10:03 ` Jan Kratochvil
2013-03-11 10:11 ` Jan Kratochvil
2013-03-11 10:13 ` Metzger, Markus T
2013-03-11 10:11 ` Metzger, Markus T
2013-03-11 13:30 ` Joel Brobecker
2013-02-20 17:44 ` Pedro Alves
2013-02-26 3:19 ` Joel Brobecker
2013-03-10 5:04 ` Hui Zhu [this message]
2013-03-10 15:48 ` Joel Brobecker
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='CANFwon1T=LuCQT2s+z8ycfKroLFKq4g+nEuwq2Br_NHsftXtPg@mail.gmail.com' \
--to=teawater@gmail.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