From: Simon Ruderich <simon@ruderich.org>
Date: Tue, 17 Apr 2012 14:52:30 +0000 (+0200)
Subject: Fix missing arguments for =item in POD.
X-Git-Tag: 0.03~20
X-Git-Url: https://ruderich.org/simon/gitweb/?p=blhc%2Fblhc.git;a=commitdiff_plain;h=96a8522b6c1015060a4ab55bdb5e94b816c93102

Fix missing arguments for =item in POD.
---

diff --git a/bin/blhc b/bin/blhc
index 6156b7d..70f814d 100755
--- a/bin/blhc
+++ b/bin/blhc
@@ -1033,17 +1033,17 @@ changes are in effect:
 
 =over 2
 
-=item
+=item *
 
 Print tags instead of normal warnings, see L</"BUILDD TAGS"> for a list of
 possible tags.
 
-=item
+=item *
 
 Don't check hardening flags in old log files (if dpkg-dev << 1.16.1 is
 detected).
 
-=item
+=item *
 
 Don't require Term::ANSIColor.
 
@@ -1129,17 +1129,13 @@ which is displayed.
 
 =over 2
 
-=item
-
-B<I-hardening-wrapper-used>
+=item B<I-hardening-wrapper-used>
 
 The package uses hardening-wrapper which intercepts calls to gcc and adds
 hardening flags. The build log doesn't contain any hardening flags and thus
 can't be checked by blhc.
 
-=item
-
-B<W-compiler-flags-hidden> (summary of hidden lines)
+=item B<W-compiler-flags-hidden> (summary of hidden lines)
 
 Build log contains lines which hide the real compiler flags. For example:
 
@@ -1153,19 +1149,13 @@ F<debian/rules> fixes builds with hidden compiler flags. Sometimes C<.SILENT>
 in a F<Makefile> must be removed. And as last resort the F<Makefile> must be
 patched to remove the C<@>s hiding the real compiler commands.
 
-=item
-
-B<W-dpkg-buildflags-missing> (summary of missing flags)
+=item B<W-dpkg-buildflags-missing> (summary of missing flags)
 
 CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS missing.
 
-=item
-
-B<I-invalid-cmake-used> (version)
-
-=item
+=item B<I-invalid-cmake-used> (version)
 
-B<I-no-compiler-commands>
+=item B<I-no-compiler-commands>
 
 No compiler commands were detected. Either the log contains none or they were
 not correctly detected by blhc (please report the bug in this case).