This is the mail archive of the gcc-bugs@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]

Re: c++/3099: cygwin: Many g++ EH failures


Hi,

Next time you follow-up to a problem report in GNATS,
please make sure that gcc-gnats@gcc.gnu.org is in
your CC: list.  That is the way that e-mails are appended
to GNATS problem reports.

On Fri, Nov 09, 2001 at 09:59:23PM -0500, Christopher Faylor wrote:
> On Sat, Nov 10, 2001 at 02:18:41AM -0000, rodrigc@gcc.gnu.org wrote:
> >Synopsis: cygwin: Many g++ EH failures
> >
> >State-Changed-From-To: feedback->closed
> >State-Changed-By: rodrigc
> >State-Changed-When: Fri Nov  9 18:18:40 2001
> >State-Changed-Why:
> >    No feedback.
> >
> >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=3099&database=gcc
> 
> Actually, feedback was provided.  It didn't make it into the PR, though:
> 
> http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg00595.html
> http://gcc.gnu.org/ml/gcc-patches/2001-06/msg01171.html
> http://gcc.gnu.org/ml/gcc-patches/2001-06/msg01156.html
> http://gcc.gnu.org/ml/gcc-patches/2001-06/msg01139.html
> 
> I don't think I ever got any further feedback from Richard after my last
> message.  That's fine, but I don't think the PR should be closed unless
> the problem is actually fixed.
> 
> And, in general, I don't think that one request for feedback with no
> reply should cause a close of the PR.
> 
> cgf


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