From: Jeffrey A Law <law@cygnus.com>
To: egcs@cygnus.com
Subject: egcs-ss-980406 is available
Date: Wed, 08 Apr 1998 02:13:00 -0000 [thread overview]
Message-ID: <365.891931405@hurl.cygnus.com> (raw)
gcs-ss-980406 is now available on
egcs.cygnus.com:/pub/egcs/snapshots/1998-04-06
(and on various mirrors, see the egcs home page for mirror sites).
You'll find:
egcs-980406.tar.gz The full egcs snapshot, including all
languages runtime libraries and
testsuites.
egcs-core-980406.tar.gz Just the C and objc language front ends.
egcs-g++-980406.tar.gz The g++ language and runtime.
egcs-g77-980406.tar.gz The g77 language and runtime.
egcs-objc-980406.tar.gz The objc runtime.
egcs-testsuite-980406.tar.gz The c & g++ testusites.
egcs-g++-testsuite-980406.tar.gz The g++ testsuite.
egcs-g77-testsuite-980406.tar.gz The g77 testsuite.
Diffs to bring the 980328 to 980406 snapshot are available.
Note if you upgraded from 980321-980328 via the snapshot diffs, then some
files in your tree are not in sync with the master sources. See the
README file in the 980406 snapshot directory for instructions on how
to get the files resynced.
Note at times you may find newer directories on the server with limited
permissions. These represent snapshots that have not yet been verified
as correct, or are known to be incorrect.
When a particular snapshot is ready for public consumption the directory
permissions are relaxed, the LATEST-IS- file is updated and a message is
sent to the egcs list.
Using a snapshot before it's officially made available is an unwise thing
to do since it may become impossible to update to an official snapshot.
jeff
reply other threads:[~1998-04-08 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=365.891931405@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.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).