aboutsummaryrefslogtreecommitdiff
path: root/binutils
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2020-01-18 13:50:25 +0000
committerNick Clifton <nickc@redhat.com>2020-01-18 13:50:25 +0000
commitae77468624a91ca149c470962c9234109c8ca105 (patch)
tree4565ca475c4c0364a7af1ab5c0ac7ac37fddc558 /binutils
parent4fb3a8daaf140ed94beef556d007013f3c5bd738 (diff)
downloadfsf-binutils-gdb-ae77468624a91ca149c470962c9234109c8ca105.zip
fsf-binutils-gdb-ae77468624a91ca149c470962c9234109c8ca105.tar.gz
fsf-binutils-gdb-ae77468624a91ca149c470962c9234109c8ca105.tar.bz2
Add markers for 2.34 branch to the NEWS files and ChangeLogs.
Diffstat (limited to 'binutils')
-rw-r--r--binutils/BRANCHES1
-rw-r--r--binutils/ChangeLog4
-rw-r--r--binutils/NEWS2
-rw-r--r--binutils/README-how-to-make-a-release12
4 files changed, 13 insertions, 6 deletions
diff --git a/binutils/BRANCHES b/binutils/BRANCHES
index b24bab7..cc84870 100644
--- a/binutils/BRANCHES
+++ b/binutils/BRANCHES
@@ -49,6 +49,7 @@ binutils-2_30-branch
binutils-2_31-branch
binutils-2_32-branch
binutils-2_33-branch
+binutils-2_34-branch
Copyright (C) 2012-2020 Free Software Foundation, Inc.
diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index ac7d86a..a84b31d 100644
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,7 @@
+2020-01-18 Nick Clifton <nickc@redhat.com>
+
+ Binutils 2.34 branch created.
+
2020-01-17 Thomas Troeger <tstroege@gmx.de>
* objdump.c (jump_info_visualize_address): Discard jumps that are
diff --git a/binutils/NEWS b/binutils/NEWS
index 92ec6bc..1650a3a 100644
--- a/binutils/NEWS
+++ b/binutils/NEWS
@@ -1,5 +1,7 @@
-*- text -*-
+Changes in 2.34:
+
* Binutils now supports debuginfod, an HTTP server for distributing
ELF/DWARF debugging information as well as source code. When built with
debuginfod, readelf and objdump can automatically query debuginfod
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 82cd27d..f011681 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -39,8 +39,8 @@ How to perform a release.
4. Create the release branch using:
- git branch binutils-2_33-branch
- git push origin binutils-2_33-branch
+ git branch binutils-2_34-branch
+ git push origin binutils-2_34-branch
If you get a message like:
@@ -50,7 +50,7 @@ How to perform a release.
5. Make sure that the branch is there. IE check out the branch sources:
- git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_33-branch 2.33
+ git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_34-branch 2.34
If you get a message about being in a "detached head" state, something
has gone wrong...
@@ -72,7 +72,7 @@ How to perform a release.
ask Joel Brobecker <brobecker AT adacore DOT com>.
7. Rename the current HEAD version entry in Bugzilla, and create a
- new one. E.g. rename "2.33 (HEAD)" to 2.33, and create "2.34
+ new one. E.g. rename "2.34 (HEAD)" to 2.34, and create "2.34
(HEAD)":
https://sourceware.org/bugzilla/editversions.cgi?product=binutils
@@ -80,13 +80,13 @@ How to perform a release.
8. Update bfd/version.m4 on HEAD to indicate that is now a snapshot
of the next release:
- m4_define([BFD_VERSION], [2.33.51])
+ m4_define([BFD_VERSION], [2.34.51])
Update the release number in bfd/version.m4 for the branch.
The branch only needs the point value set to 90 as the release
has not actually happened yet.
- m4_define([BFD_VERSION], [2.32.90])
+ m4_define([BFD_VERSION], [2.33.90])
Regenerate various files on both branch and HEAD by configuring
with "--enable-maintainer-mode --enable-gold" and then building