From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Joel Brobecker <brobecker@adacore.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: GDB 7.7 branching on Monday?
Date: Thu, 19 Dec 2013 22:29:00 -0000 [thread overview]
Message-ID: <CAMe9rOpp9=t_fJyn=9gPix_GJvKhLqZvgSh5e0rEanF7ssyDAQ@mail.gmail.com> (raw)
In-Reply-To: <201312192151.rBJLpr1i015135@glazunov.sibelius.xs4all.nl>
On Thu, Dec 19, 2013 at 1:51 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Thu, 19 Dec 2013 10:06:36 -0800
>> From: "H.J. Lu" <hjl.tools@gmail.com>
>>
>> On Thu, Dec 19, 2013 at 9:59 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > Hello,
>> >
>> > I think the last known issue on the TODO list before branching
>> > (see TODO at https://sourceware.org/gdb/wiki/GDB_7.7_Release)
>> > should be checked in today, or this weekend at the latest.
>> >
>> > Unless there are some other issues we haven't listed yet, I propose
>> > to create the branch on Monday morning.
>> >
>>
>> I have 4 patches I like to see in GDB 7.7:
>>
>> https://sourceware.org/ml/gdb-patches/2013-12/msg00313.html
>
> This one is defenitely ok; thanks for revising it.
>
> The other three look reasonable, but I'm really not familliar enough
> with the instruction set to review these diffs. And I don't use that
> code myself. So you should probably just go ahead.
>
I checked 4 patches in. Thanks for reviewing them.
--
H.J.
next prev parent reply other threads:[~2013-12-19 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 17:59 Joel Brobecker
2013-12-19 18:06 ` H.J. Lu
2013-12-19 18:22 ` Joel Brobecker
2013-12-19 18:27 ` H.J. Lu
2013-12-19 21:52 ` Mark Kettenis
2013-12-19 22:29 ` H.J. Lu [this message]
2013-12-19 20:31 ` Sergio Durigan Junior
2013-12-20 3:28 ` Joel Brobecker
2013-12-20 3:37 ` Sergio Durigan Junior
2013-12-25 4:48 ` Sergio Durigan Junior
2013-12-28 3:11 ` Joel Brobecker
2013-12-23 8:01 ` Joel Brobecker
2014-01-07 2:54 ` Joel Brobecker
2014-01-07 23:44 ` Pierre Muller
2013-12-24 21:22 Nick Bull
2013-12-25 2:47 ` 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='CAMe9rOpp9=t_fJyn=9gPix_GJvKhLqZvgSh5e0rEanF7ssyDAQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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