mirror/gcc
1
0
Fork 0
mirror of https://github.com/gcc-mirror/gcc.git synced 2024-11-21 13:40:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

maintainer-scripts/gcc_release: cleanup whitespace

Browse Source 
maintainer-scripts/
	* gcc_release: Cleanup whitespace.

Signed-off-by: Sam James <sam@gentoo.org>
This commit is contained in:
Sam James 2023-11-02 08:39:08 +00:00 committed by Joseph Myers
parent 3239a80555
commit d22b87864e
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
maintainer-scripts/gcc_release
View File

@ -153,7 +153,7 @@ build_sources() {
# Update this ChangeLog file only if it does not yet contain the # 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 # entry we are going to add. (This is a safety net for repeated
# runs of this script for the same release.) # 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 <<EOF cat - ${SOURCE_DIRECTORY}/${x} > ${SOURCE_DIRECTORY}/${x}.new <<EOF
${LONG_DATE} Release Manager ${LONG_DATE} Release Manager
@ -278,7 +278,7 @@ EOF
# Create a "MD5SUMS" file to use for checking the validity of the release. # Create a "MD5SUMS" file to use for checking the validity of the release.
echo \ echo \
"# This file contains the MD5 checksums of the files in the "# This file contains the MD5 checksums of the files in the
# gcc-"${RELEASE}".tar.xz tarball. # gcc-"${RELEASE}".tar.xz tarball.
# #
# Besides verifying that all files in the tarball were correctly expanded, # Besides verifying that all files in the tarball were correctly expanded,
@ -323,7 +323,7 @@ build_tarfiles() {
chmod -R a+r ${SOURCE_DIRECTORY} chmod -R a+r ${SOURCE_DIRECTORY}
# And that all directories have mode 755. # And that all directories have mode 755.
find ${SOURCE_DIRECTORY} -type d -exec chmod 755 {} \; find ${SOURCE_DIRECTORY} -type d -exec chmod 755 {} \;
# Build one huge tarfile for the entire distribution. # Build one huge tarfile for the entire distribution.
build_tarfile gcc-${RELEASE} `basename ${SOURCE_DIRECTORY}` build_tarfile gcc-${RELEASE} `basename ${SOURCE_DIRECTORY}`
} }
@ -442,7 +442,7 @@ snapshot_print() {
# Announce a snapshot, both on the web and via mail. # Announce a snapshot, both on the web and via mail.
announce_snapshot() { announce_snapshot() {
inform "Updating links and READMEs on the FTP server" inform "Updating links and READMEs on the FTP server"
TEXT_DATE=`date --date=$DATE +%B\ %d,\ %Y` TEXT_DATE=`date --date=$DATE +%B\ %d,\ %Y`
SNAPSHOT_README=${RELEASE}/README SNAPSHOT_README=${RELEASE}/README
SNAPSHOT_INDEX=${RELEASE}/index.html SNAPSHOT_INDEX=${RELEASE}/index.html
@ -472,7 +472,7 @@ You'll find:
<p>The <a href =\"https://gcc.gnu.org/\">GCC Project</a> makes <p>The <a href =\"https://gcc.gnu.org/\">GCC Project</a> makes
periodic snapshots of the GCC source tree available to the public periodic snapshots of the GCC source tree available to the public
for testing purposes.</p> for testing purposes.</p>
<p>If you are planning to download and use one of our snapshots, then <p>If you are planning to download and use one of our snapshots, then
we highly recommend you join the GCC developers list. Details for we highly recommend you join the GCC developers list. Details for
how to sign up can be found on the GCC project home page.</p> how to sign up can be found on the GCC project home page.</p>
@ -481,7 +481,7 @@ how to sign up can be found on the GCC project home page.</p>
with the following options: <code>"git://gcc.gnu.org/git/gcc.git branch ${GITBRANCH} revision ${GITREV}"</code></p> with the following options: <code>"git://gcc.gnu.org/git/gcc.git branch ${GITBRANCH} revision ${GITREV}"</code></p>
<table>" > ${SNAPSHOT_INDEX} <table>" > ${SNAPSHOT_INDEX}
snapshot_print gcc-${RELEASE}.tar.xz "Complete GCC" snapshot_print gcc-${RELEASE}.tar.xz "Complete GCC"
echo \ echo \
@ -548,7 +548,7 @@ FTP_PATH=/var/ftp/pub/gcc
# The directory in which snapshots will be placed. # The directory in which snapshots will be placed.
SNAPSHOTS_DIR=${FTP_PATH}/snapshots 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' # `3'
RELEASE_MAJOR="" RELEASE_MAJOR=""
# The minor number for the release. For release `3.0.2' this would be # 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. # The complete name of the release.
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. # user-friendly form.
BRANCH="" BRANCH=""