summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2011-12-21 10:22:17 +0100
committerNicholas Clark <nick@ccl4.org>2011-12-21 10:22:17 +0100
commitace6885803467dcfa5af494c1215d0faa0042f88 (patch)
tree68e71b9ce8b0c3b2167476d09196026de330db8f
parent06c2f2362c7cd7b500f7f68241c6c189f0566fe4 (diff)
downloadperl-ace6885803467dcfa5af494c1215d0faa0042f88.tar.gz
Lazier instructions for removing stale perldeltas for 5.x.0-RC0
The previous instructions were unaware that most of what they describe is already automated.
-rw-r--r--Porting/release_managers_guide.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index f13f37d2fe..2ee69c9290 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -396,10 +396,10 @@ For example, for RC0 of 5.16.0:
$ cd pod
$ git rm perldelta515*.pod
-All mention to them should also be removed. Currently the files that
-need to be edited for this task are F<MANIFEST>,
-F<pod/perl.pod>, and F<win32/pod.mak> (including C<.man>, C<.html>, and
-C<.tex> entries for each removed pod).
+All mention to them should also be removed. Edit F<pod/perl.pod> to remove
+them from its table of contents, then run F<Porting/pod_rules.pl> to
+propagate your changes there into all the other files that mention them
+(including F<MANIFEST>). You'll need to C<git add> the files that it changes.
Then build a clean perl and do a full test