From: Jeffrey A Law <law@cygnus.com>
To: Oleg Krivosheev <kriol@fnal.gov>
Cc: egcs@cygnus.com
Subject: Re: Release Status
Date: Fri, 31 Oct 1997 15:51:00 -0000 [thread overview]
Message-ID: <10030.878342017@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.GSO.3.96.971031001618.900A-100000@drabble>
In message < Pine.GSO.3.96.971031001618.900A-100000@drabble >you write:
> > So, here is the outstanding issues that need to be resolved before the
> > first release.
>
> Any words/ideas about what have to be fixed in libstdc++
> to be ready for first erlease?
I'm not aware of anything that's critical enough to fix for
this release.
jeff
next prev parent reply other threads:[~1997-10-31 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-30 20:16 Jeffrey A Law
1997-10-30 14:17 ` Joe Buck
1997-10-30 22:23 ` Oleg Krivosheev
1997-10-31 15:51 ` Jeffrey A Law [this message]
1997-10-31 6:27 Max Lawson
1998-09-02 1:50 Release status Jeffrey A Law
1998-09-03 4:22 ` Carlo Wood
1998-09-03 5:16 ` Jeffrey A Law
1998-09-03 5:16 ` SL Baur
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=10030.878342017@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=kriol@fnal.gov \
/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).