Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Steve Ellcey <sellcey@imgtec.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 7.9 branching - 2 weeks to go (Mon, Jan 12th)!
Date: Tue, 06 Jan 2015 16:38:00 -0000	[thread overview]
Message-ID: <20150106163804.GK5445@adacore.com> (raw)
In-Reply-To: <1420560568.15691.25.camel@ubuntu-sellcey>

> I think PR gdb/17718 should be considered a blocking bug because it
> breaks the builds on some systems (depending on what version of GCC is
> used to build).

It should not break the build, actually, because releases are configured
to make --disable-werror the default. The change is performed as soon as
the branch is cut. So we should be OK.

-- 
Joel


      reply	other threads:[~2015-01-06 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  7:15 Joel Brobecker
2014-12-30 15:42 ` Eli Zaretskii
2014-12-30 15:51   ` Joel Brobecker
2014-12-31 18:11 ` Jan Kratochvil
2015-01-05  4:10 ` Joel Brobecker
2015-01-05  4:13   ` Doug Evans
2015-01-05  4:17     ` Joel Brobecker
2015-01-05 16:07   ` Eli Zaretskii
2015-01-06 16:09 ` Steve Ellcey
2015-01-06 16:38   ` Joel Brobecker [this message]

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=20150106163804.GK5445@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sellcey@imgtec.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