From: Tom Tromey <tromey@redhat.com>
To: Michael Eager <eager@eagerm.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: gdb-7.6 branch build failures
Date: Mon, 28 Oct 2013 18:29:00 -0000 [thread overview]
Message-ID: <8738nlckrb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <526E8D82.4080700@eagerm.com> (Michael Eager's message of "Mon, 28 Oct 2013 09:14:58 -0700")
>>>>> "Michael" == Michael Eager <eager@eagerm.com> writes:
Michael> Is anyone building gdb_7_6-branch without these errors?
Michael> If not, I'll submit a patch for the branch to turn off
Michael> -Werror for these files.
If the fix is straightforward, I suggest just back-porting it instead.
Tom
next prev parent reply other threads:[~2013-10-28 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 16:15 Michael Eager
2013-10-28 18:29 ` Tom Tromey [this message]
2013-10-28 18:42 ` Michael Eager
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=8738nlckrb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@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