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: Tue, 29 Oct 2002 08:56:00 -0000	[thread overview]
Message-ID: <20021029165602.9643.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@nabi.net (B. Kosnik)
Cc: Joe.Buck@synopsys.COM (Joe Buck), bkoz@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
   gcc-bugs@gcc.gnu.org, peter@snake.iap.physik.tu-darmstadt.de
Subject: Re: libstdc++/6745: Sever io problems on branch rdbuf
Date: Tue, 29 Oct 2002 08:47:56 -0800 (PST)

 I wrote:
 > >So, we still have a bug, but we no longer have a regression: this stuff
 > >works as well as it ever did.
 
 Benjamin Kosnik writes:
 > Again, I intend to look at this, but at the moment I am on the road. I
 > should be able to work on this at the end of this week.
 
 Since 6745 is no longer a regression, it seems that Mark would have to
 make an exception to the rules to even accept a patch for the branch.
 
 6746, also assigned to you, has higher priority.  It is a regression.
 


             reply	other threads:[~2002-10-29 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29  8:56 Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29  1:56 paolo
2002-10-29  5:56 B. Kosnik
2002-10-28 11:16 Joe Buck
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=20021029165602.9643.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).