public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Ranjit Mathew <rmathew@hotmail.com>,
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: PATCH for Re: Today's snapshot
Date: Wed, 28 May 2003 14:38:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.55.0305281318460.53379@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.53.0305281153490.7368@kern.srcf.societies.cam.ac.uk>

On Wed, 28 May 2003, Joseph S. Myers wrote:
> But that's not the file to patch: it's snapshot-README and
> snapshot-index.html in CVS that are to be patched, not the generated
> files on the FTP site.

Sheesh, I forget that you cleaned that up. :-(

2003-05-28  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* snapshot-README: Refer to .bz2 files instead of .gz files.
	Add a note on where to find the diff files.
	Simplify the note on not using unannounced snapshots.
	Remove documentation of the gcc_latest_snapshot tag.

Index: snapshot-README
===================================================================
RCS file: /cvs/gcc/gcc/maintainer-scripts/snapshot-README,v
retrieving revision 1.7
diff -u -3 -p -r1.7 snapshot-README
--- snapshot-README	16 Dec 2002 22:18:33 -0000	1.7
+++ snapshot-README	28 May 2003 11:22:05 -0000
@@ -6,36 +6,26 @@ This snapshot has been generated from th

 You'll find:

-  gcc-@DATE@.tar.gz                  The full gcc snapshot, including all
+  gcc-@DATE@.tar.bz2                 The full gcc snapshot, including all
                                        languages runtime libraries.

-  gcc-core-@DATE@.tar.gz             Just the C front end and core compiler.
+  gcc-core-@DATE@.tar.bz2            Just the C front end and core compiler.

-  gcc-testsuite-@DATE@.tar.gz        The GCC testsuite.
+  gcc-testsuite-@DATE@.tar.bz2       The GCC testsuite.

-  gcc-ada-@DATE@.tar.gz              The Ada language and runtime.
+  gcc-ada-@DATE@.tar.bz2             The Ada language and runtime.

-  gcc-g++-@DATE@.tar.gz              The g++ language and runtime.
+  gcc-g++-@DATE@.tar.bz2             The g++ language and runtime.

-  gcc-g77-@DATE@.tar.gz              The g77 language and runtime.
+  gcc-g77-@DATE@.tar.bz2             The g77 language and runtime.

-  gcc-objc-@DATE@.tar.gz             The Objective-C front end and runtime.
+  gcc-objc-@DATE@.tar.bz2            The Objective-C front end and runtime.

-  gcc-java-@DATE@.tar.gz             The Java front end.
+  gcc-java-@DATE@.tar.bz2            The Java front end.

-Diffs from @LAST_DATE@ are available.
+Diffs from @LAST_DATE@ are available in the diffs/ subdirectory.

-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.
+When a particular snapshot is ready for public consumption the LATEST-IS-
+file is updated and a message is sent to the gcc list.  Please do not use
+a snapshot before it has been announced that way.

  reply	other threads:[~2003-05-28 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 16:59 Gerald Pfeifer
2003-05-27  5:20 ` Ranjit Mathew
2003-05-27  9:39   ` Gerald Pfeifer
2003-05-27 10:01     ` Joseph S. Myers
2003-05-28 13:47       ` Gerald Pfeifer
2003-05-28 14:01         ` Joseph S. Myers
2003-05-28 14:38           ` Gerald Pfeifer [this message]
2003-05-27 11:55     ` Ranjit Mathew

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.55.0305281318460.53379@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    --cc=rmathew@hotmail.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).