Felix Lechner pushed to branch master at lintian / lintian
Commits: 4eb3bc4f by Daniel Kahn Gillmor at 2022-03-08T19:14:03-05:00 Correct lintian-annotate-hints manpage Without this change, the pod2man-generated output generates a verbatim section of troff: .PP .Vb 4 \& (Note, though, that the B<lintian> command has a command line option \&B<\-i> to display the same results as B<lintian\-annotate\-hints>, so you \&normally do not need to pipe the output of B<lintian> through this \&command to see the extra information.) .Ve .SH "OPTIONS" With the change, it produces the following roff data, including the expected formatting: .PP (Note, though, that the \fBlintian\fR command has a command line option \&\fB\-i\fR to display the same results as \fBlintian-annotate-hints\fR, so you normally do not need to pipe the output of \fBlintian\fR through this command to see the extra information.) .SH "OPTIONS" I believe this is because pod2man treats leading a indents as indicative of a verbatim section. - - - - - 1 changed file: - man/lintian-annotate-hints.pod Changes: ===================================== man/lintian-annotate-hints.pod ===================================== @@ -40,7 +40,7 @@ its input on stdin. Thus, the output of B<lintian> can either be piped through B<lintian-annotate-hints> or a log file produced by B<lintian> can be processed with this command. - (Note, though, that the B<lintian> command has a command line option +(Note, though, that the B<lintian> command has a command line option B<-i> to display the same results as B<lintian-annotate-hints>, so you normally do not need to pipe the output of B<lintian> through this command to see the extra information.) View it on GitLab: https://salsa.debian.org/lintian/lintian/-/commit/4eb3bc4fde134b17e0abdd3b1f886b52be7cdea2 -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/commit/4eb3bc4fde134b17e0abdd3b1f886b52be7cdea2 You're receiving this email because of your account on salsa.debian.org.
