This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC Release Status (2003-08-03)

From: "Mark Mitchell" <mark at codesourcery dot com>
To: "Daniel Berlin" <dberlin at dberlin dot org>
Cc: "Joe Buck" <jbuck at synopsys dot com>,<gcc at gcc dot gnu dot org>
Date: Tue, 5 Aug 2003 17:43:47 -0700
Subject: Re: GCC Release Status (2003-08-03)
Organization: CodeSourcery, LLC
References: <200308031612.h73GCSQq005684@doubledemon.codesourcery.com> <5EAA1F02-C5F9-11D7-8E11-000A95A34564@dberlin.org> <20030804093551.B24974@synopsys.com> <003701c35b01$ad73fae0$1e1eab83@minax> <A191274C-C6F6-11D7-BBD5-000A95A34564@dberlin.org>

> I can add this feature if you guys really want it, I just see it as a
> "don't do that" type thing that we're all smart enough not to do.  Why
> would a developer target a new bug at an old release?
> Remember, users can't target bugs to milestones.

I'm smart, but I've made mistakes before.

The computer should be able to keep me from making this particular mistake.

The failure mode is that a bug goes into everlasting limbo, which would
hardly say good things about our quality processes.

Therefore, if you can make the computer keep me out of trouble, that would
be good.

Thanks,

-- Mark

References:
- GCC Release Status (2003-08-03)
  - From: Mark Mitchell
- Re: GCC Release Status (2003-08-03)
  - From: Daniel Berlin
- Re: GCC Release Status (2003-08-03)
  - From: Joe Buck
- Re: GCC Release Status (2003-08-03)
  - From: Mark Mitchell
- Re: GCC Release Status (2003-08-03)
  - From: Daniel Berlin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]