public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7543: Suggest new warning message for gcc
Date: Mon, 10 Mar 2003 20:56:00 -0000	[thread overview]
Message-ID: <20030310205600.18280.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/7543; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/7543: Suggest new warning message for gcc
Date: Mon, 10 Mar 2003 14:46:47 -0600 (CST)

 ---------- Forwarded message ----------
 Date: Fri, 7 Mar 2003 11:43:55 -0500 (EST)
 From: Tom Truscott <trt@unx.sas.com>
 To: bangerth@dealii.org
 Subject: Re: c/7543: Suggest new warning message for gcc
 
 >     Tom, did your patch get applied to CVS? What's the state of
 >     this?
 
 I don't know if it was applied, but I strongly doubt it.
 
 The state of this is totally defunct.
 I have tried different request strategies for a few years
 and have concluded that only if I become a gcc insider
 can I get even the simplest changes made.
 I don't have the time, energy, or interest in that.
 
 I'm content with the dozens of a warnings I've added
 to my personal copy of gcc, which I run daily
 to spot problems in my company's product (20M+ LOC).
 
 If there is a gcc insider who would like to shepherd
 specific warning changes I will be happy to supply them.
 Beyond that I'm not interested, not even in discussing this,
 so feel to mark this bug NOFIX or whatever.
 
 Thanks,
 Tom Truscott
 


             reply	other threads:[~2003-03-10 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 20:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-10 20:50 bangerth
2003-03-07  2:48 bangerth
2002-08-08  9:16 trt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030310205600.18280.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).