From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: GDB 7.7 branching on Monday?
Date: Thu, 19 Dec 2013 18:27:00 -0000 [thread overview]
Message-ID: <CAMe9rOp202t4m1jmiNT=cGSng3cniNj__F81eJpv_63L6vLtcQ@mail.gmail.com> (raw)
In-Reply-To: <20131219182206.GI3493@adacore.com>
On Thu, Dec 19, 2013 at 10:22 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> I have 4 patches I like to see in GDB 7.7:
>>
>> https://sourceware.org/ml/gdb-patches/2013-12/msg00309.html
>> https://sourceware.org/ml/gdb-patches/2013-12/msg00307.html
>> https://sourceware.org/ml/gdb-patches/2013-12/msg00313.html
>> https://sourceware.org/ml/gdb-patches/2013-12/msg00310.html
>
> I'll need a little more from you. What's your estimate for getting them
As you said, they are small changes. But I don't know when
Mark will have time to review them.
> in, and what are the consequences of not having them for 7.7?
Reverse debugging won't work for x32 without them.
> Here is what I propose: We go ahead with the branch on Monday.
> Looking at the patches, they seem to be relatively simple enough
> that they should be good candidates for backporting to the branch
> if they get approved after Monday.
>
It sounds good to me.
BTW, what can/should GDB community do to reduce review time
for x86 specific changes, especially those small changes.
Thanks.
--
H.J.
next prev parent reply other threads:[~2013-12-19 18:27 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 [this message]
2013-12-19 21:52 ` Mark Kettenis
2013-12-19 22:29 ` H.J. Lu
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='CAMe9rOp202t4m1jmiNT=cGSng3cniNj__F81eJpv_63L6vLtcQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).