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++/712: bad formatting of warning message

To: Craig Rodrigues <rodrigc at mediaone dot net>
Subject: Re: c++/712: bad formatting of warning message
From: Tom Tromey <tromey at redhat dot com>
Date: 20 Aug 2001 20:54:11 -0600
Cc: Gabriel Dos Reis <gdr at codesourcery dot com>, rodrigc at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org
References: <20010728221219.31892.qmail@sourceware.cygnus.com> <874rr2tvx9.fsf@creche.redhat.com> <fl4rr2tx12.fsf@jambon.cmla.ens-cachan.fr> <20010820201817.A9569@mediaone.net>
Reply-To: tromey at redhat dot com

>>>>> "Craig" == Craig Rodrigues <rodrigc@mediaone.net> writes:

Craig> Any bug tracking system should definitely try to age out bug
Craig> reports where feedback is not provided after many months of
Craig> waiting.

I believe it would be possible -- even easy -- to write a small
program to do exactly this.  I don't really have the time to do it.
But, I could provide some pointers if someone is interested.  I think
this would be a useful contribution to Gnats.

Tom

References:
- Re: c++/712: bad formatting of warning message
  - From: Tom Tromey
- Re: c++/712: bad formatting of warning message
  - From: Gabriel Dos Reis
- Re: c++/712: bad formatting of warning message
  - From: Craig Rodrigues

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