public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kanze@gabi-soft.de, nobody@gcc.gnu.org Subject: Re: libstdc++/4686: Output disappearing after operator<<( streambuf* ) Date: Thu, 25 Oct 2001 23:35:00 -0000 [thread overview] Message-ID: <20011026063517.2647.qmail@sourceware.cygnus.com> (raw) Synopsis: Output disappearing after operator<<( streambuf* ) Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Thu Oct 25 23:35:16 2001 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Thu Oct 25 23:35:16 2001 State-Changed-Why: Hmm. Can you try this today (2001-10-25)? I cann't reproduce this with mainline CVS (gcc-3.1) -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4686&database=gcc
next reply other threads:[~2001-10-25 23:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-25 23:35 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-13 15:24 rodrigc 2001-10-25 21:06 Carlo Wood 2001-10-25 16:28 kanze
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=20011026063517.2647.qmail@sourceware.cygnus.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=kanze@gabi-soft.de \ --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: linkBe 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).