public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: optimization/4490
Date: Fri, 25 Apr 2003 00:46:00 -0000	[thread overview]
Message-ID: <20030425004601.22793.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: rth@gnu.gcc.org
Cc: gcc-gnats@gcc.gnu.org
Subject: optimization/4490
Date: Thu, 24 Apr 2003 19:43:29 -0500 (CDT)

 Richard,
 I just closed a report for which I found that it is a duplicate of 4490. 
 What startles me with that one is that it is suspended. What is the reason 
 for that? If this just waits for someone to fix it, I think we'd better 
 leave it analyzed. "suspended" only seems like the proper choice when we 
 are waiting for external events to happen (resolution of a standard defect 
 report, branch to merge, etc).
 
 Thanks
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-04-25  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25  0:46 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 15:26 optimization/4490 Wolfgang Bangerth
2003-04-25  3:36 optimization/4490 Richard Henderson
2003-04-25  0:46 optimization/4490 Wolfgang Bangerth
2001-10-08  6:36 optimization/4490 Reichelt

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=20030425004601.22793.qmail@sources.redhat.com \
    --to=bangerth@ices.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).