[binutils-gdb] Update the how-to-make-a-release document so that a check for empty manual pages is included. cf PR

Nick Clifton nickc@sourceware.org
Tue Aug 31 10:20:39 GMT 2021


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=88ae41e17980533927f98339bcb40015522f06c4

commit 88ae41e17980533927f98339bcb40015522f06c4
Author: Nick Clifton <nickc@redhat.com>
Date:   Tue Aug 31 11:19:56 2021 +0100

    Update the how-to-make-a-release document so that a check for empty manual pages is included.  cf PR 28144

Diff:
---
 binutils/README-how-to-make-a-release | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 19ae2b24f53..7aa5efa0497 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -232,6 +232,10 @@ When the time comes to actually make the release....
 
            tar tvf binutils-2.37.tar.bz2 | grep -e "---"
 
+      Also check that the man files are not empty.  (cf PR 28144).
+
+           tar tvf binutils-2.37.tar.xz | grep -e "\.1"
+
   25. Sanity check the release on x86_64-pc-linux-gnu by building and
       running the testsuites (gas, gold, binutils and ld).  Make the
       source directory read-only before building.  Also test


More information about the Binutils-cvs mailing list