From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Set --disable-werror by default again for the release?
Date: Mon, 04 Dec 2006 20:32:00 -0000 [thread overview]
Message-ID: <u4psbcsi2.fsf@gnu.org> (raw)
In-Reply-To: <20061204182442.GB11343@adacore.com> (message from Joel Brobecker on Mon, 4 Dec 2006 10:24:42 -0800)
> Date: Mon, 4 Dec 2006 10:24:42 -0800
> From: Joel Brobecker <brobecker@adacore.com>
>
> Because C compilers vary a lot in the warnings they emit, and newer
> compilers always find newer warnings, I am starting to think that
> we might want to produce all our released with --disable-werror by
> default. More work for me, but less hassle for the users...
>
> What does everyone think?
I think you should leave it as it is for the pretest duration, so we
could catch as many of these problems as we could, and then use
"--disable-werror" in the actual release.
prev parent reply other threads:[~2006-12-04 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 18:25 Joel Brobecker
2006-12-04 18:47 ` David Daney
2006-12-04 20:32 ` Eli Zaretskii [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=u4psbcsi2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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