public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Stein Somers <ssomers@opnet.com>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6795: stringbuf failure
Date: Mon, 27 May 2002 12:22:00 -0000	[thread overview]
Message-ID: <20020527191601.14015.qmail@sources.redhat.com> (raw)

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

From: Stein Somers <ssomers@opnet.com>
To: bkoz@gcc.gnu.org, bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, ssomers@opnet.com,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/6795: stringbuf failure
Date: Mon, 27 May 2002 21:11:41 +0200

 At 27-05-02 11:37 +0000, you wrote:
 >Synopsis: stringbuf failure
 >
 >Responsible-Changed-From-To: unassigned->bkoz
 >Responsible-Changed-By: bkoz
 >Responsible-Changed-When: Mon May 27 04:37:54 2002
 >Responsible-Changed-Why:
 >     Mine.
 >State-Changed-From-To: open->feedback
 >State-Changed-By: bkoz
 >State-Changed-When: Mon May 27 04:37:54 2002
 >State-Changed-Why:
 
 Yes, that solves the problem!  Now all of my tests succeed.  Thanks.
 
 Probably a silly remark - I have no prior experience with cvs and how the 
 gcc team uses it - but I've checked out the sources with "-r 
 cvs_latest_snapshot" and without -r, and both gave the old version, so I 
 corrected it manually.
 
 Stein
 


             reply	other threads:[~2002-05-27 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 12:22 Stein Somers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29  2:26 Benjamin Kosnik
2002-05-29  2:02 bkoz
2002-05-27  4:46 bkoz

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=20020527191601.14015.qmail@sources.redhat.com \
    --to=ssomers@opnet.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).