This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch branching.html: defaulting to --disable-checking/--disable-werror
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 22 Jan 2003 01:12:34 +0000 (GMT)
- Subject: Re: Patch branching.html: defaulting to --disable-checking/--disable-werror
On Tue, 21 Jan 2003, Kaveh R. Ghazi wrote:
> I don't think we've been very consistent in the past on this topic.
>
> And there are plusses and minuses to doing this earlier and later.
>
> Obviouly we want extra checks up until the last minute. But recall
> when we were close to releasing 3.0, we turned off checking only to
> find that a major bug turned up only with checking turned off. So
> it's also good to test exactly the code you intend to release and not
> something "pretty close to it" as the checking toggles create.
If things are to be done at the start of a branch, there's no need for a
manual action in branching.html - having configure extract the development
status from doc/include/gcc-common.texi would be better, to reduce the
number of files needing changing when creating a branch.
--
Joseph S. Myers
jsm28@cam.ac.uk