From c7a3a5b4b9527250c5493344fcb0e75d0d33dcb8 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 4 Apr 2015 20:48:54 -0600 Subject: [PATCH] Regen podcheck db Commit a81f7519ba607e6fb9838391ed0be7603c01ca2b fixed a problem in perlvms. --- t/porting/known_pod_issues.dat | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index 1e6f214..12a0f6f 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -1,4 +1,4 @@ -# This file is the data file for t/porting/podcheck.t. +# This file is the data file for porting/podcheck.t. # There are three types of lines. # Comment lines are white-space only or begin with a '#', like this one. Any # changes you make to the comment lines will be lost when the file is @@ -311,7 +311,6 @@ pod/perltie.pod Verbatim line length including indents exceeds 79 by 13 pod/perltrap.pod ? Should you be using F<...> or maybe L<...> instead of 1 pod/perltru64.pod ? Should you be using F<...> or maybe L<...> instead of 1 pod/perltru64.pod Verbatim line length including indents exceeds 79 by 5 -pod/perlvms.pod ? Should you be using F<...> or maybe L<...> instead of 1 pod/perlwin32.pod Verbatim line length including indents exceeds 79 by 12 porting/epigraphs.pod Verbatim line length including indents exceeds 79 by 16 porting/expand-macro.pl Verbatim line length including indents exceeds 79 by 2 -- 1.8.3.1