From: Jason Merrill <jason@cygnus.com>
To: mrs@wrs.com (Mike Stump), egcs@cygnus.com
Subject: Re: egcs-971201: testsuite results for i586-pc-linux-gnulibc1
Date: Tue, 02 Dec 1997 21:12:00 -0000 [thread overview]
Message-ID: <u9g1obaukw.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199712030125.RAA06256.cygnus.egcs@kankakee.wrs.com>
>>>>> Mike Stump <mrs@wrs.com> writes:
> Ok, I already mentioned the fix for the g++.jason/destruct3.C problem,
> it is really safe, I think it should be included in the release.
Sorry I overlooked it for so long. I've put it into the trunk, but it's
not critical enough for the release at this point.
Jason
next parent reply other threads:[~1997-12-02 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712030125.RAA06256.cygnus.egcs@kankakee.wrs.com>
1997-12-02 21:12 ` Jason Merrill [this message]
1997-12-02 18:18 Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 9:56 Max Lawson
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=u9g1obaukw.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mrs@wrs.com \
/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).