public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6745: Sever io problems on branch rdbuf
Date: Mon, 28 Oct 2002 11:16:00 -0000	[thread overview]
Message-ID: <20021028191602.11196.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/6745; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: bkoz@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   peter@snake.iap.physik.tu-darmstadt.de
Cc:  
Subject: Re: libstdc++/6745: Sever io problems on branch rdbuf
Date: Mon, 28 Oct 2002 11:06:39 -0800

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6745
 
 I'm going to downgrade the priority of this PR to "medium".  The reason 
 is based
 on Paolo's comment:
 
  > After private mail with Benjamin we believe that this PR
  > unfortunately must be kept open. In fact, the behaviour of
  > v2 is restored but something is still NOT ok in this area.
 
 So, we still have a bug, but we no longer have a regression: this stuff
 works as well as it ever did.
 
 So this one should not hold up 3.2.1.  Unfortunately, there are about 15
 other high-priority PRs.
 


             reply	other threads:[~2002-10-28 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 11:16 Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29  1:56 paolo
2002-10-29  8:56 Joe Buck
2002-10-29  5:56 B. Kosnik
2002-10-24  0:56 paolo
2002-10-23 15:03 jbuck
2002-05-29  5:06 bkoz
2002-05-20 14:09 paolo
2002-05-20  9:56 peter

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=20021028191602.11196.qmail@sources.redhat.com \
    --to=jbuck@synopsys.com \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-prs@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).