public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: gccadmin@gcc.gnu.org
To: gcc@gcc.gnu.org
Subject: gcc-ss-20020819 is now available
Date: Mon, 19 Aug 2002 17:22:00 -0000	[thread overview]
Message-ID: <20020820002221.11768.qmail@sources.redhat.com> (raw)

gcc-ss-20020819 is now available on 
  ftp://gcc.gnu.org/pub/gcc/snapshots/2002-08-19
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 3.2 branch.

You'll find:

  gcc-20020819.tar.gz                  The full gcc snapshot, including all
                                       languages runtime libraries.

  gcc-core-20020819.tar.gz             Just the C front end and core compiler.

  gcc-testsuite-20020819.tar.gz        The GCC testsuite.

  gcc-ada-20020819.tar.gz              The Ada language and runtime.

  gcc-g++-20020819.tar.gz              The g++ language and runtime.

  gcc-g77-20020819.tar.gz              The g77 language and runtime.

  gcc-objc-20020819.tar.gz             The Objective-C front end and runtime.

  gcc-java-20020819.tar.gz             The Java front end.

Diffs from 20020812 are available.

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 gcc 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.

The "gcc_latest_snapshot" tag has been moved.  You can use
cvs update -rgcc_latest_snapshot to update your CVS tree to the latest
official snapshot.

                 reply	other threads:[~2002-08-19 17:22 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=20020820002221.11768.qmail@sources.redhat.com \
    --to=gccadmin@gcc.gnu.org \
    --cc=gcc@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).