This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: bugzilla clean ups
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: Bud Davis <bdavis9659 at sbcglobal dot net>, "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
- Date: Sat, 15 Jun 2013 11:17:14 -0700
- Subject: Re: bugzilla clean ups
- References: <1371250719 dot 95250 dot YahooMailClassic at web182206 dot mail dot bf1 dot yahoo dot com> <CAF1jjLtxvU67PftpcqHUhNsywgpmUF8ZV1DUWpFtnMpOMphgew at mail dot gmail dot com>
On Sat, Jun 15, 2013 at 02:03:16PM -0400, NightStrike wrote:
> On Fri, Jun 14, 2013 at 6:58 PM, Bud Davis <bdavis9659@sbcglobal.net> wrote:
> > Hello All,
> >
> > There are some bug reports in bugzilla that are old and stale...what are the rules for closing them as "WONT FIX".
> >
> > The first example I ran across was
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22210
> >
> > Not too sure of the original problem, but it has been 6+ years.
> >
> > Can I terminate this one (and ones like it) ?
> >
> > Should some discussion hit the mailing list ?
>
> [Resending to list, caught in html mail trap]
>
> Just because a big hasn't been fixed in a while doesn't mean it should be
> closed. So no you should not just close old bugs as won't fix for the sole
> reason that they are old.
I think what you meant to write is "If the old bug is still present, then
one should not close the bug report. If the old bug cannot be reproduced
then the report should be closed."
--
Steve