In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/c7a3a5b4b9527250c5493344fcb0e75d0d33dcb8?hp=a81f7519ba607e6fb9838391ed0be7603c01ca2b>
- Log ----------------------------------------------------------------- commit c7a3a5b4b9527250c5493344fcb0e75d0d33dcb8 Author: Karl Williamson <[email protected]> Date: Sat Apr 4 20:48:54 2015 -0600 Regen podcheck db Commit a81f7519ba607e6fb9838391ed0be7603c01ca2b fixed a problem in perlvms. M t/porting/known_pod_issues.dat commit e8a0e562cfe59ba7c0319daa427850eb51f8e68d Author: Karl Williamson <[email protected]> Date: Sat Apr 4 20:48:27 2015 -0600 perlpodspec: Nit M pod/perlpodspec.pod ----------------------------------------------------------------------- Summary of changes: pod/perlpodspec.pod | 2 +- t/porting/known_pod_issues.dat | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod index 20a9195..f8d1901 100644 --- a/pod/perlpodspec.pod +++ b/pod/perlpodspec.pod @@ -625,7 +625,7 @@ literal byte value 0xFF 0xFE, this is the BOM for little-endian UTF-16. On an ASCII platform, if the file begins with the three literal byte values 0xEF 0xBB 0xBF, this is the BOM for UTF-8. -(A mechanism portable to EBCDIC platforms is to: +A mechanism portable to EBCDIC platforms is to: my $utf8_bom = "\x{FEFF}"; utf8::encode($utf8_bom); 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 -- Perl5 Master Repository
