In perl.git, the branch blead has been updated
<http://perl5.git.perl.org/perl.git/commitdiff/21768cb3b7803f58d5e8a4d116f01abe3014272c?hp=872fa9285df6b08c0a53ae598448a8b85b2721a8>
- Log -----------------------------------------------------------------
commit 21768cb3b7803f58d5e8a4d116f01abe3014272c
Author: Father Chrysostomos <spr...@cpan.org>
Date: Fri Jun 10 13:27:21 2011 -0700
Correct example commit in release_managers_guide.pod; add example
The 8891dd8d commit mentioned in the perlNNNdelta section is actually
an example of a perl version bump. So Iâve copied it to that section
and replaced the commit id in the perlNNNdelta section with dd885b5,
which *is* a perlNNNdelta TOC update.
M Porting/release_managers_guide.pod
commit a15bfc9e2304470503968445191dc51fa75f3b82
Author: Father Chrysostomos <spr...@cpan.org>
Date: Fri Jun 10 13:20:23 2011 -0700
Regenerate known_pod_issues.dat
I think thereâs a bug in podchecker, as it seems to be counting octets
instead of characters in README.tw.
M t/porting/known_pod_issues.dat
-----------------------------------------------------------------------
Summary of changes:
Porting/release_managers_guide.pod | 8 ++++++--
t/porting/known_pod_issues.dat | 1 +
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Porting/release_managers_guide.pod
b/Porting/release_managers_guide.pod
index e6ca378..35e136b 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -308,6 +308,10 @@ Commit your changes:
$ git commit -a -m 'Bump the perl version in various places for 5.x.y'
+At this point you may want to compare the commit with a previous bump to
+see if they look similar. See commit 8891dd8d for an example of a
+previous version bump.
+
When the version number is bumped, you should also update Module::CoreList
(as described below in L<"update Module::CoreList">) to reflect the new
version number.
@@ -962,8 +966,8 @@ Finally, commit:
$ git commit -a -m 'update TOC for perlNNNdelta'
-At this point you may want to compare the commit with a previous bump to
-see if they look similar. See commit 8891dd8d for an example of a
+At this point you may want to compare the commit with a previous bump to
+see if they look similar. See commit dd885b5 for an example of a
previous version bump.
diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index 1717388..6126716 100644
--- a/t/porting/known_pod_issues.dat
+++ b/t/porting/known_pod_issues.dat
@@ -312,6 +312,7 @@ pod/perltrap.pod ? Should you be using F<...> or maybe
L<...> instead of 1
pod/perltrap.pod Verbatim line length including indents exceeds 80 by
15
pod/perltru64.pod ? Should you be using F<...> or maybe L<...> instead of
1
pod/perltru64.pod Verbatim line length including indents exceeds 80 by
4
+pod/perltw.pod Verbatim line length including indents exceeds 80 by 2
pod/perlunicode.pod Verbatim line length including indents exceeds 80 by
16
pod/perlunifaq.pod ? Should you be using L<...> instead of 1
pod/perlunifaq.pod empty section in previous paragraph 1
--
Perl5 Master Repository
