Remove trailing spaces in binutils/README-how-to-make-a-release

binutils/ChangeLog:

        * README-how-to-make-a-release: Remove trailing spaces.

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index dafa8e6..d5eb885 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,7 @@
+2018-01-16  Joel Brobecker  <brobecker@adacore.com>
+
+       * README-how-to-make-a-release: Remove trailing spaces.
+
 2018-01-15  Nick Clifton  <nickc@redhat.com>
 
        * po/uk.po: Updated Ukranian translation.

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index ce1af8f..83159f7 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -1,5 +1,5 @@
                README for MAKING BINUTILS RELEASES
-       
+
 This is a collection of notes on how to perform a binutils release.  A
 lot of this information can also be found in the maintain.texi file in
 the gnulib project:
@@ -22,21 +22,21 @@ How to perform a release.
   1. Send an email out warning contributors about the forthcoming
      branch.  Set a date for the branch (weekends are better because
      they are less busy).
-  
+
   2. Update the libiberty and config directories and the top level
-     configure files.  
+     configure files.
 
   3. When branch day arrives add markers for the upcoming release to
      gas, ld, gold and binutils NEWS files.
        [If using the make-prerelease.sh script, check that
-        common.sh has the right values].       
+        common.sh has the right values].
        [make-prelease.sh command i]
        [make-prelease.sh command C]
      Likewise for all of the ChangeLog files.
      Add a note of the name of the new branch to binutils/BRANCHES.
      Commit these changes.
        [make-prerelease.sh command C]
-     
+
   4. Create the release branch using:
 
        git tag -a binutils-2_30-branch   [eg for the 2.30 branch...]
@@ -64,9 +64,9 @@ How to perform a release.
         the files, and check this in.
 
      b. Create a source tarball of the branch sources:
-     
+
            ./src-release -x binutils
- 
+
      c. Build a test target using this tarball.
 
      d. Upload the prerelease snapshot to the FTP:
@@ -75,9 +75,9 @@ How to perform a release.
           ssh sourceware.org md5sum ~ftp/pub/binutils/snapshots/binutils-$version.tar.xz
 
    9. Send it to the Translation Project:
-   
+
         http://translationproject.org/html/maintainers.html
-       
+
       Sending mail for one of the POT files is sufficient.
 
   10. Announce the availability of the snapshot and the branch on the
@@ -113,9 +113,9 @@ looks like this:
 
   2.5 Prepare a list of the bugs which have been fixed.  This
       will be needed for step 8.
-      
+
   3. In the branch sources:
-  
+
        a. Update the minor release number in bfd/version.m4.
        b. Edit bfd/development.sh and set "development=false".
        c. Regenerate the configure files.
@@ -131,13 +131,13 @@ looks like this:
           correct file permissions.  Eg:
 
            umask 022
-       
+
        g. Create the release tarballs:
             ./src-release -b -g -l -x binutils
 
        h. Check that the files in the tarballs have the correct
           permissions.
-       
+
        i. Edit bfd/development.sh and set "development=true".
        j. Commit this change into the git repository.
        k. Clean up the source tree.  (Use "git status" to find new
@@ -148,7 +148,7 @@ looks like this:
 
   4. [If paranoid - upload the tarballs to one of the FTP servers and
       ask people to test it before going on to step 5].
-      
+
   5. Upload the tarballs to ftp.gnu.org.
 
        gnupload --to ftp.gnu.org:binutils binutils-X.XX.X.tar.*
@@ -184,7 +184,7 @@ Hi Everyone,
 
   We are pleased to announce that version 2.XX.X of the Binutils project
   sources have been released and are now available for download at:
-  
+
     https://ftp.gnu.org/gnu/binutils
     https://sourceware.org/pub/binutils/releases/