summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames E Keenan <jkeenan@cpan.org>2019-06-21 10:48:42 -0400
committerSteve Hay <steve.m.hay@googlemail.com>2020-05-14 18:24:45 +0100
commitd6329cfa4de1937807bc099080f1857592c5db5a (patch)
treed95d496f85184a66493630537d61b23d3c62e288
parentbb1346d038318a4706b9671f83516978b36e85f6 (diff)
downloadperl-d6329cfa4de1937807bc099080f1857592c5db5a.tar.gz
Add two entries to pod issues database
Two diagnostic one-liners were added to release manager's guide. They exceeded POD line length limits and were not easily breakable. Hence, added to list of exceptions. (cherry picked from commit e29a253e189dde26f93283ee93b3b8e44d46b7a3)
-rw-r--r--t/porting/known_pod_issues.dat2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index e89d5c02a1..9150a823b5 100644
--- a/t/porting/known_pod_issues.dat
+++ b/t/porting/known_pod_issues.dat
@@ -374,7 +374,7 @@ pod/perltie.pod Verbatim line length including indents exceeds 79 by 3
pod/perltru64.pod Verbatim line length including indents exceeds 79 by 1
pod/perlwin32.pod Verbatim line length including indents exceeds 79 by 7
porting/epigraphs.pod Verbatim line length including indents exceeds 79 by -1
-porting/release_managers_guide.pod Verbatim line length including indents exceeds 79 by 1
+porting/release_managers_guide.pod Verbatim line length including indents exceeds 79 by 2
porting/todo.pod ? Should you be using F<...> or maybe L<...> instead of 1
lib/benchmark.pm Verbatim line length including indents exceeds 79 by 2
lib/config.pod ? Should you be using L<...> instead of -1