Add markers for 2.40 branch

[thirdparty/binutils-gdb.git] / binutils / README-how-to-make-a-release

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 4b93303bb32c556d4e27efbb39aed0bb96abc994..e81b410d64f51b70a79349cc1294942d9659de72 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -32,14 +32,13 @@ Approx time to complete from here: 2 hours ....
 
   2.5 If you have not built from the sources recently then now is the
       time to check that they still work...
-      
+
   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
      in the gold directory - it has its own release numbering.
 
      Likewise for the ChangeLog files in: bfd, binutils, config, cpu,
-     elfcpp, gas, gold, gprof, include, ld, libctf, libiberty, opcodes
-     and toplevel.
+     elfcpp, gas, gold, gprof, include, ld, libctf, opcodes and toplevel.
 
      Add a note of the name of the new branch to binutils/BRANCHES.