• R/O
  • HTTP
  • SSH
  • HTTPS

提交

標籤
無標籤

Frequently used words (click to add to your profile)

javac++androidlinuxc#windowsobjective-ccocoa誰得qtpythonphprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer

GNU Binutils with patches for OS216


Commit MetaInfo

修訂e256144888a28eae9326f86cd95282b807aa2f6a (tree)
時間2018-08-01 23:52:32
作者Nick Clifton <nickc@redh...>
CommiterNick Clifton

Log Message

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.

Change Summary

差異

--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
1+2018-08-01 Nick Clifton <nickc@redhat.com>
2+
3+ * README-how-to-make-a-release: Add note about regenerating the
4+ info files prior to the release.
5+
16 2018-07-30 Andrew Jenner <andrew@codesourcery.com>
27
38 * MAINTAINERS (C-SKY): Add Yunhai Shang as co-maintainer.
--- 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....
165165 branch to a whole new minor version number, without a point
166166 value. Eg "2.29.90" becomes "2.30". Change bfd/development.sh
167167 to set the value to "false". Regenerate the configure and
168- makefiles. Add ChangeLog entries for the updates and add a
169- "this-is-the-2.XX-release" comment and commit. Make sure to
170- include the .gmo files.
168+ makefiles. And *info* files. Add ChangeLog entries for the
169+ updates and add a "this-is-the-2.XX-release" comment and
170+ commit. Make sure to include the .gmo files.
171171
172172 22. Check that your file creation mask will create the
173173 correct file permissions. Eg: