From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Nitish Kumar Mishra <mishra.nitish.88@gmail.com>,
Tremblay <antoine.tremblay@ericsson.com>,
Keith Seitz <keiths@redhat.com>,
"Wiederhake, Tim" <tim.wiederhake@intel.com>
Subject: Re: GDB 8.0 release/branching 2017-03-20 update
Date: Mon, 20 Mar 2017 22:47:00 -0000 [thread overview]
Message-ID: <CAH=s-POkr=yqoNMxwEfCUmg9wxBC=3T=pL=a+400caGQ77v4tw@mail.gmail.com> (raw)
In-Reply-To: <CAH=s-PP5HtpcGxGVBQ7eYaO_reV=GggZ6eVv5Nhs8kChNJHVLQ@mail.gmail.com>
On Mon, Mar 20, 2017 at 10:39 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
>> * [TimWiederhake] Build issue when using Python 2.6.x
>>
>> What's the status of that patch? My questions were answered,
>> but was the patch reviewed?
>>
>> https://www.sourceware.org/ml/gdb-patches/2017-03/msg00053.html
>>
>
> I've already conditionally approved the patch, with a fix in
> doc part, "Python 3" or "@code{Python} 3". Tim's patch uses
> the former but I suggested the latter. Tim believes "Python 3"
> should be used (off-list) so I asked Eli
> https://sourceware.org/ml/gdb-patches/2017-03/msg00334.html
>
Just got Eli's reply. Tim's patch can go in without any changes.
I'll take care of this patch if Tim is unreachable.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-03-20 22:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:16 Joel Brobecker
2017-03-20 20:21 ` Keith Seitz
2017-03-20 22:39 ` Yao Qi
2017-03-20 22:47 ` Yao Qi [this message]
2017-03-20 22:52 ` Joel Brobecker
2017-03-20 23:03 ` Yao Qi
2017-03-21 13:28 ` Joel Brobecker
2017-03-21 7:35 ` Wiederhake, Tim
2017-03-21 13:28 ` Joel Brobecker
2017-03-21 13:07 ` Yao Qi
2017-03-21 13:31 ` Joel Brobecker
2017-03-22 13:58 ` Metzger, Markus T
2017-03-22 17:09 ` Yao Qi
2017-03-23 16:01 ` Metzger, Markus T
2017-03-23 17:25 ` Yao Qi
2017-03-23 18:17 ` Metzger, Markus T
2017-03-24 14:41 ` Yao Qi
2017-03-27 10:51 ` Metzger, Markus T
2017-03-27 11:19 ` Yao Qi
2017-03-27 12:46 ` Metzger, Markus T
2017-03-27 16:03 ` Yao Qi
2017-03-28 7:16 ` Metzger, Markus T
2017-03-28 13:25 ` Yao Qi
2017-03-28 15:08 ` Metzger, Markus T
2017-03-28 15:49 ` Yao Qi
2017-03-29 6:08 ` Metzger, Markus T
[not found] ` <861stgo072.fsf@gmail.com>
2017-03-29 14:38 ` Metzger, Markus T
2017-03-30 10:50 ` Yao Qi
2017-03-30 11:58 ` Metzger, Markus T
[not found] ` <86h92a4w86.fsf@gmail.com>
2017-03-30 15:55 ` Metzger, Markus T
2017-03-31 13:55 ` Yao Qi
2017-03-31 15:21 ` Metzger, Markus T
2017-03-31 16:02 ` Joel Brobecker
2017-04-06 14:40 ` Wiederhake, Tim
2017-04-07 8:10 ` Yao Qi
2017-04-07 11:53 ` Wiederhake, Tim
2017-04-07 15:19 ` Yao Qi
2017-03-21 14:00 ` Yao Qi
2017-03-21 14:03 ` Pedro Alves
2017-03-27 13:35 ` Antoine Tremblay
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='CAH=s-POkr=yqoNMxwEfCUmg9wxBC=3T=pL=a+400caGQ77v4tw@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=antoine.tremblay@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=mishra.nitish.88@gmail.com \
--cc=tim.wiederhake@intel.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