From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: [for 7.8?] Re: --with-babeltrace generates many FAILs
Date: Tue, 26 Aug 2014 20:27:00 -0000 [thread overview]
Message-ID: <20140826202741.GA9143@host2.jankratochvil.net> (raw)
In-Reply-To: <87iolltca9.fsf@codesourcery.com>
On Fri, 22 Aug 2014 05:48:30 +0200, Yao Qi wrote:
> Patch is pushed in. Thanks.
Maybe could you push it also for 7.8.1?
https://sourceware.org/gdb/wiki/GDB_7.8_Release
At least I have pushed there first the CFLAGS=-Wall fix which disclosed this
bug a bit more.
Jan
next prev parent reply other threads:[~2014-08-26 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140816204614.GA7000@host2.jankratochvil.net>
2014-08-19 12:43 ` Yao Qi
2014-08-19 14:08 ` Jan Kratochvil
2014-08-20 4:06 ` Yao Qi
2014-08-20 9:41 ` Pedro Alves
2014-08-20 11:38 ` Yao Qi
2014-08-20 13:56 ` Pedro Alves
2014-08-21 4:57 ` Yao Qi
2014-08-21 12:48 ` Pedro Alves
2014-08-22 3:52 ` Yao Qi
2014-08-26 20:27 ` Jan Kratochvil [this message]
2014-08-27 8:27 ` [for 7.8?] " Yao Qi
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=20140826202741.GA9143@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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