diff options
| author | Nick Clifton <nickc@redhat.com> | 2019-01-19 15:55:50 +0000 |
|---|---|---|
| committer | Nick Clifton <nickc@redhat.com> | 2019-01-19 15:55:50 +0000 |
| commit | f974f26cb16cc6fe3946f163c787a05e713fb77b (patch) | |
| tree | 8eb780c1070e23072489db4deefa80fc22fce1de /binutils | |
| parent | f3be6050c8d62d59a1846dacda5f895c5b0f9dbc (diff) | |
| download | gdb-f974f26cb16cc6fe3946f163c787a05e713fb77b.zip gdb-f974f26cb16cc6fe3946f163c787a05e713fb77b.tar.gz gdb-f974f26cb16cc6fe3946f163c787a05e713fb77b.tar.bz2 | |
Add markers for 2.32 branch to NEWS and ChangeLog files.
Diffstat (limited to 'binutils')
| -rw-r--r-- | binutils/BRANCHES | 1 | ||||
| -rw-r--r-- | binutils/ChangeLog | 4 | ||||
| -rw-r--r-- | binutils/NEWS | 2 | ||||
| -rw-r--r-- | binutils/README-how-to-make-a-release | 12 |
4 files changed, 13 insertions, 6 deletions
diff --git a/binutils/BRANCHES b/binutils/BRANCHES index ec8ca50..63f1e84 100644 --- a/binutils/BRANCHES +++ b/binutils/BRANCHES @@ -47,6 +47,7 @@ binutils-2_28-branch binutils-2_29-branch binutils-2_30-branch binutils-2_31-branch +binutils-2_32-branch Copyright (C) 2012-2019 Free Software Foundation, Inc. diff --git a/binutils/ChangeLog b/binutils/ChangeLog index 2e17bab..345cbc5 100644 --- a/binutils/ChangeLog +++ b/binutils/ChangeLog @@ -1,3 +1,7 @@ +2018-06-24 Nick Clifton <nickc@redhat.com> + + 2.32 branch created. + 2019-01-17 Nick Clifton <nickc@redhat.com> * objdump.c (disassemble_section): When disassembling from a diff --git a/binutils/NEWS b/binutils/NEWS index 0b8cc8e..9ea8297 100644 --- a/binutils/NEWS +++ b/binutils/NEWS @@ -1,5 +1,7 @@ -*- text -*- +Changes in 2.32: + * The addr2line, c++filt, nm and objdump tools now have a limit on the maximum amount of recursion that is allowed whilst demangling strings. The value for this limit is defined by the DEMANGLE_RECRUSE_LIMIT diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release index 60fd5be..aec5486 100644 --- a/binutils/README-how-to-make-a-release +++ b/binutils/README-how-to-make-a-release @@ -27,14 +27,14 @@ How to perform a release. directories and the top level configure files. 3. When branch day arrives add markers for the upcoming release to - gas, ld, gold and binutils NEWS files. - [If using the make-prerelease.sh script, check that - common.sh has the right values]. - [make-prelease.sh command i] - Likewise for all of the ChangeLog files. + the NEWS files in gas, ld, gold and binutils. + + Likewise for the ChangeLog files in: bfd, binutils, config, cpu, + elfcpp, gas, gold, gprof, include, ld, opcodes and toplevel. + Add a note of the name of the new branch to binutils/BRANCHES. + Commit these changes. - [make-prerelease.sh command C] 4. Create the release branch using: |