public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/19747] [meta-bug] : cris-elf libstdc++ testsuite failures as of "Tue Feb 1 22:03:59 UTC 2005"
Date: Sun, 27 Feb 2005 06:55:00 -0000 [thread overview]
Message-ID: <20050226183254.15365.qmail@sourceware.org> (raw)
In-Reply-To: <20050202011123.19747.hp@gcc.gnu.org>
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-02-26 18:32:51
date| |
Summary|meta: cris-elf libstdc++ |[meta-bug] : cris-elf
|testsuite failures as of |libstdc++ testsuite failures
|"Tue Feb 1 22:03:59 UTC |as of "Tue Feb 1 22:03:59
|2005" |UTC 2005"
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19747
next prev parent reply other threads:[~2005-02-26 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 1:11 [Bug libstdc++/19747] New: meta: " hp at gcc dot gnu dot org
2005-02-27 6:55 ` pinskia at gcc dot gnu dot org [this message]
[not found] <bug-19747-507@http.gcc.gnu.org/bugzilla/>
2006-12-12 13:10 ` [Bug libstdc++/19747] [meta-bug] : " bkoz at gcc dot gnu dot org
2007-03-29 12:01 ` steven at gcc dot gnu dot org
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=20050226183254.15365.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).