summaryrefslogtreecommitdiff
path: root/t/porting
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2015-03-24 22:03:15 -0700
committerFather Chrysostomos <sprout@cpan.org>2015-03-24 22:03:27 -0700
commit12cfc3ac0d36a97eddefa925ba09d0b21feb23a0 (patch)
treec55e8004c3c6e1021528248320850e1188300af3 /t/porting
parentf942a0dfa923e36f91c00b44e21563cd50dc750b (diff)
downloadperl-12cfc3ac0d36a97eddefa925ba09d0b21feb23a0.tar.gz
regen pod issues
Diffstat (limited to 't/porting')
-rw-r--r--t/porting/known_pod_issues.dat3
1 files changed, 2 insertions, 1 deletions
diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index 7d538533c6..2f39815d9a 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 porting/podcheck.t.
+# This file is the data file for t/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
@@ -278,6 +278,7 @@ pod/perlgit.pod Verbatim line length including indents exceeds 79 by 12
pod/perlgpl.pod Verbatim line length including indents exceeds 79 by 50
pod/perlguts.pod ? Should you be using F<...> or maybe L<...> instead of 2
pod/perlguts.pod ? Should you be using L<...> instead of 1
+pod/perlguts.pod Verbatim line length including indents exceeds 79 by 1
pod/perlhack.pod ? Should you be using L<...> instead of 1
pod/perlhist.pod Verbatim line length including indents exceeds 79 by 1
pod/perlhpux.pod Verbatim line length including indents exceeds 79 by 7