From: Karl Williamson Date: Wed, 21 Aug 2013 21:33:52 +0000 (-0600) Subject: RMG: Fix some verbatim lines over 79 columns X-Git-Tag: v5.19.4~477 X-Git-Url: https://perl5.git.perl.org/perl5.git/commitdiff_plain/ed3803055ee53367e2749347d7516245e1944e20 RMG: Fix some verbatim lines over 79 columns --- diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 9759b25..569b1ad 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -323,23 +323,23 @@ C instead. Ensure dual-life CPAN modules are stable, which comes down to: - for each module that fails its regression tests on $current - did it fail identically on $previous? - if yes, "SEP" (Somebody Else's Problem) - else work out why it failed (a bisect is useful for this) - - attempt to group failure causes - - for each failure cause - is that a regression? - if yes, figure out how to fix it - (more code? revert the code that broke it) - else - (presumably) it's relying on something un-or-under-documented - should the existing behaviour stay? - yes - goto "regression" - no - note it in perldelta as a significant bugfix - (also, try to inform the module's author) + for each module that fails its regression tests on $current + did it fail identically on $previous? + if yes, "SEP" (Somebody Else's Problem) + else work out why it failed (a bisect is useful for this) + + attempt to group failure causes + + for each failure cause + is that a regression? + if yes, figure out how to fix it + (more code? revert the code that broke it) + else + (presumably) it's relying on something un-or-under-documented + should the existing behaviour stay? + yes - goto "regression" + no - note it in perldelta as a significant bugfix + (also, try to inform the module's author) =head3 monitor smoke tests for failures @@ -403,24 +403,24 @@ to guarantee binary compatibility in maint branches. After editing, regenerate uconfig.h (this must be run on a system with a /bin/sh available): - $ perl regen/uconfig_h.pl + $ perl regen/uconfig_h.pl This might not cause any new changes. Test your changes: - $ git clean -xdf # careful if you don't have local files to keep! - $ ./Configure -des -Dusedevel - $ make - $ make test + $ git clean -xdf # careful if you don't have local files to keep! + $ ./Configure -des -Dusedevel + $ make + $ make test Commit your changes: - $ git status - $ git diff - B + $ git status + $ git diff + B - $ git commit -a -m 'Bump the perl version in various places for 5.x.y' + $ 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 f7cf42bb69 for an example of a @@ -856,13 +856,13 @@ up. Create a tarball. Use the C<-s> option to specify a suitable suffix for the tarball and directory name: - $ cd root/of/perl/tree - $ make distclean - $ git clean -xdf # make sure perl and git agree on files - $ git status # and there's nothing lying around + $ cd root/of/perl/tree + $ make distclean + $ git clean -xdf # make sure perl and git agree on files + $ git status # and there's nothing lying around - $ perl Porting/makerel -b -s RC1 # for a release candidate - $ perl Porting/makerel -b # for a final release + $ perl Porting/makerel -b -s RC1 # for a release candidate + $ perl Porting/makerel -b # for a final release This creates the directory F<../perl-x.y.z-RC1> or similar, copies all the MANIFEST files into it, sets the correct permissions on them, then @@ -1253,9 +1253,9 @@ I Copy the perldelta.pod for this release into blead; for example: - $ cd ..../blead - $ cp -i ../5.10.x/pod/perldelta.pod pod/perl5101delta.pod # for example - $ git add pod/perl5101delta.pod + $ cd ..../blead + $ cp -i ../5.10.x/pod/perldelta.pod pod/perl5101delta.pod # for example + $ git add pod/perl5101delta.pod Edit F to add an entry for the file, e.g.: diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index 12c2b15..22eceaa 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -269,7 +269,7 @@ 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 2 porting/expand-macro.pl Verbatim line length including indents exceeds 79 by 2 -porting/release_managers_guide.pod Verbatim line length including indents exceeds 79 by 7 +porting/release_managers_guide.pod Verbatim line length including indents exceeds 79 by 5 porting/todo.pod Verbatim line length including indents exceeds 79 by 7 utils/c2ph Verbatim line length including indents exceeds 79 by 44 lib/benchmark.pm Verbatim line length including indents exceeds 79 by 2