diff --git a/maintainer-scripts/gcc_release b/maintainer-scripts/gcc_release index 9d8aa3babd6..42bb7f68f17 100755 --- a/maintainer-scripts/gcc_release +++ b/maintainer-scripts/gcc_release @@ -153,7 +153,7 @@ build_sources() { # Update this ChangeLog file only if it does not yet contain the # entry we are going to add. (This is a safety net for repeated # runs of this script for the same release.) - if ! grep "GCC ${RELEASE} released." ${SOURCE_DIRECTORY}/${x} > /dev/null ; then + if ! grep "GCC ${RELEASE} released." ${SOURCE_DIRECTORY}/${x} > /dev/null ; then cat - ${SOURCE_DIRECTORY}/${x} > ${SOURCE_DIRECTORY}/${x}.new <The GCC Project makes periodic snapshots of the GCC source tree available to the public for testing purposes.

- +

If you are planning to download and use one of our snapshots, then we highly recommend you join the GCC developers list. Details for how to sign up can be found on the GCC project home page.

@@ -481,7 +481,7 @@ how to sign up can be found on the GCC project home page.

with the following options: "git://gcc.gnu.org/git/gcc.git branch ${GITBRANCH} revision ${GITREV}"

" > ${SNAPSHOT_INDEX} - + snapshot_print gcc-${RELEASE}.tar.xz "Complete GCC" echo \ @@ -548,7 +548,7 @@ FTP_PATH=/var/ftp/pub/gcc # The directory in which snapshots will be placed. SNAPSHOTS_DIR=${FTP_PATH}/snapshots -# The major number for the release. For release `3.0.2' this would be +# The major number for the release. For release `3.0.2' this would be # `3' RELEASE_MAJOR="" # The minor number for the release. For release `3.0.2' this would be @@ -560,7 +560,7 @@ RELEASE_REVISION="" # The complete name of the release. RELEASE="" -# The name of the branch from which the release should be made, in a +# The name of the branch from which the release should be made, in a # user-friendly form. BRANCH=""