aboutsummaryrefslogtreecommitdiff
path: root/binutils/README-how-to-make-a-release
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2018-08-01 15:51:57 +0100
committerNick Clifton <nickc@redhat.com>2018-08-01 15:52:32 +0100
commite256144888a28eae9326f86cd95282b807aa2f6a (patch)
tree40fd98de0096925dac23dec9ef4fd695fffbde61 /binutils/README-how-to-make-a-release
parente30985fa2b495a6b932e1376f287cb51252572d7 (diff)
downloadgdb-e256144888a28eae9326f86cd95282b807aa2f6a.zip
gdb-e256144888a28eae9326f86cd95282b807aa2f6a.tar.gz
gdb-e256144888a28eae9326f86cd95282b807aa2f6a.tar.bz2
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.
Diffstat (limited to 'binutils/README-how-to-make-a-release')
-rw-r--r--binutils/README-how-to-make-a-release6
1 files changed, 3 insertions, 3 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 3759538..c58515a 100644
--- 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: