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: your RESOLVED->CLOSED changes

From: DJ Delorie <dj at redhat dot com>
To: bangerth at ices dot utexas dot edu
Cc: neroden at twcny dot rr dot com, gcc at gcc dot gnu dot org
Date: Fri, 23 May 2003 16:01:37 -0400
Subject: Re: your RESOLVED->CLOSED changes
References: <Pine.LNX.4.44.0305231445160.13914-100000@gandalf.ices.utexas.edu>

In the cases you're talking about, the cron job would automatically
close the PR shortly after it's fixed.  This doesn't require extra
people at all.

In the cases I'm talking about, the originator would have a window of
opportunity to test the fix and reject it if it doesn't happen to fix
it for them.  I've been burned too many times with my bug reports (er,
not gcc, but for other projects) being closed without being fixed, and
without me getting any say in it.

Follow-Ups:
- Re: your RESOLVED->CLOSED changes
  - From: Wolfgang Bangerth

References:
- Re: your RESOLVED->CLOSED changes
  - From: Wolfgang Bangerth

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