From: Karl Williamson Date: Sat, 18 Jun 2011 20:34:55 +0000 (-0600) Subject: File::Find pod: fix link issue X-Git-Tag: accepted/trunk/20130322.191538~3609 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f4d05d5f5d33ca0c43ac538cc7c55f19815809b2;p=platform%2Fupstream%2Fperl.git File::Find pod: fix link issue --- diff --git a/lib/File/Find.pm b/lib/File/Find.pm index cdcf97e..f2fe20b 100644 --- a/lib/File/Find.pm +++ b/lib/File/Find.pm @@ -3,7 +3,7 @@ use 5.006; use strict; use warnings; use warnings::register; -our $VERSION = '1.19'; +our $VERSION = '1.20'; require Exporter; require Cwd; @@ -114,7 +114,7 @@ Causes symbolic links to be followed. Since directory trees with symbolic links (followed) may contain files more than once and may even have cycles, a hash has to be built up with an entry for each file. This might be expensive both in space and time for a large -directory tree. See I and I below. +directory tree. See L and L below. If either I or I is in effect: =over 6 diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index dda9878..708630b 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -345,7 +345,6 @@ lib/extutils/embed.pm Verbatim line length including indents exceeds 80 by 2 lib/extutils/xssymset.pm Verbatim line length including indents exceeds 80 by 1 lib/file/basename.pm ? Should you be using L<...> instead of 1 lib/file/basename.pm Verbatim line length including indents exceeds 80 by 2 -lib/file/find.pm ? Should you be using L<...> instead of 1 lib/file/find.pm Verbatim line length including indents exceeds 80 by 1 lib/getopt/std.pm Verbatim line length including indents exceeds 80 by 1 lib/perlio.pm Verbatim line length including indents exceeds 80 by 2