Add a note about regenerating the info files when creating a new release.

	* README-how-to-make-a-release: Add note about regenerating the
	info files prior to the release.

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index c47a9d8..ad7a87c 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+2018-08-01  Nick Clifton  <nickc@redhat.com>
+
+       * README-how-to-make-a-release: Add note about regenerating the
+       info files prior to the release.
+
 2018-07-30  Andrew Jenner  <andrew@codesourcery.com>
 
        * MAINTAINERS (C-SKY): Add Yunhai Shang as co-maintainer.

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 3759538..c58515a 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -165,9 +165,9 @@ When the time comes to actually make the release....
       branch to a whole new minor version number, without a point
       value.  Eg "2.29.90" becomes "2.30".  Change bfd/development.sh
       to set the value to "false".  Regenerate the configure and
-      makefiles.  Add ChangeLog entries for the updates and add a
-      "this-is-the-2.XX-release" comment and commit.  Make sure to
-      include the .gmo files.
+      makefiles.  And *info* files.  Add ChangeLog entries for the
+      updates and add a  "this-is-the-2.XX-release" comment and
+      commit.  Make sure to include the .gmo files.
 
   22. Check that your file creation mask will create the
       correct file permissions.  Eg: