This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Named warnings
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Richard dot Earnshaw at arm dot com
- Cc: Falk Hueffner <falk dot hueffner at student dot uni-tuebingen dot de>, Mark Mitchell <mark at codesourcery dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: 24 Jan 2003 19:38:16 +0100
- Subject: Re: RFC: Named warnings
- Organization: Integrable Solutions
- References: <200301241812.h0OICiT17110@pc960.cambridge.arm.com>
Richard Earnshaw <rearnsha@arm.com> writes:
| > Richard Earnshaw <rearnsha@arm.com> writes:
| >
| > | That's easily solved. Just declare the master file to be the mainline. A
| > | warning number is never added on a branch without first adding it to the
| > | mainline (note: it's only the number that's added on the trunk).
| >
| > This means that when mainline is frozen, no warning number can be
| > added to branches.
|
| There's no real reason why that file should be frozen for that purpose.
|
| Anyway, most freezes that exceed a few hours occur only on branches.
Well, last time mainline was frozen for a week (at least) -- there
were various (good) reasons.
-- Gaby