From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-announce@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: Changes concerning GCC snapshots (and releases)
Date: Wed, 02 Jul 2003 22:13:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.56.0307022328340.53953@acrux.dbai.tuwien.ac.at> (raw)
For some time now, I have been working to update how our weekly snapshots
(as we distribute them from ftp://gcc.gnu.org/pub/gcc/snapshots and many
mirror sites) are run, and have already made the following changes:
o Weekly snapshots are only available in .bz2 format, which allows
for noticeably smaller archives.
o We abandoned and removed the gcc_latest_snapshot CVS tag.
o Diff files now reside in a subdirectory "diffs/" of the respective
snapshot directories.
The last item also applies to future releases of GCC, which we will
continue to ship in both .gz and .bz2 formats.
In addition, I am working on the following further changes:
o The names of the snapshot directories shall include the name of the
relevant branch in GCC's CVS repository or the string "mainline" in
addition to the date.
For example, while the last snapshot was labelled gcc_ss_20030630,
the next one probably will be labelled gcc-ss-3_3-20030707.
o Later, this will also apply to individual archive files.
o And, finally, we want to provide snapshots both off mainline and the
currently active release branch (currently, the 3.3 branch).
If you have any questions, comments, or complaints concerning these
changes, please do not hesitate to let us know.
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
reply other threads:[~2003-07-02 22: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=Pine.BSF.4.56.0307022328340.53953@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=gcc-announce@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).