aboutsummaryrefslogtreecommitdiff
path: root/binutils/README-how-to-make-a-release
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2021-01-09 10:40:28 +0000
committerNick Clifton <nickc@redhat.com>2021-01-09 10:40:28 +0000
commit055bc77a80b333ec68c373719b54aee6c232995b (patch)
tree3267db9aa2089d3df2a77724a5e36023c7fecb80 /binutils/README-how-to-make-a-release
parentce0be4070f04ff8295a3cb58e352f759ce8ae70d (diff)
downloadgdb-055bc77a80b333ec68c373719b54aee6c232995b.zip
gdb-055bc77a80b333ec68c373719b54aee6c232995b.tar.gz
gdb-055bc77a80b333ec68c373719b54aee6c232995b.tar.bz2
Add Changelog entries and NEWS entries for 2.36 branch
Diffstat (limited to 'binutils/README-how-to-make-a-release')
-rw-r--r--binutils/README-how-to-make-a-release3
1 files changed, 2 insertions, 1 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index d732541..8f91f31 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -24,7 +24,8 @@ How to perform a release.
they are less busy).
2. When the branch date is near: Update the libiberty and config
- directories and the top level configure files.
+ directories and the top level Makefile and configure files. Also
+ consider updating the toplevel libtool files.
3. When branch day arrives add markers for the upcoming release to
the NEWS files in gas, ld, and binutils. No need to update NEWS