From: Rafael Garcia-Suarez Date: Thu, 13 Jul 2006 08:17:04 +0000 (+0000) Subject: Additions to perlhack based on a patch by Gabor Szabo X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=824d470babf4b508f3fdcda470d1e5f15aa9650a;p=p5sagit%2Fp5-mst-13.2.git Additions to perlhack based on a patch by Gabor Szabo p4raw-id: //depot/perl@28562 --- diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 37a6a7e..a2c989e 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -598,14 +598,24 @@ ftp://ftp.gnu.org/pub/gnu/ , or use Johan Vromans' I but context diffs are accepted. Do not send RCS-style diffs or diffs without context lines. More information is given in the I file in the Perl source distribution. Please -patch against the latest B version (e.g., if you're -fixing a bug in the 5.005 track, patch against the latest 5.005_5x -version). Only patches that survive the heat of the development +patch against the latest B version. (e.g., even if you're +fixing a bug in the 5.8 track, patch against the latest B +version rsynced from rsync://public.activestate.com/perl-current/ ) + +If changes are accepted, they are applied to the development branch. Then +the 5.8 pumpking decides which of those patches is to be backported to the +maint branch. Only patches that survive the heat of the development branch get applied to maintenance versions. -Your patch should update the documentation and test suite. See +Your patch should also update the documentation and test suite. See L. +Patching documentation also follows the same order: if accepted, a patch +is first applied to B, and if relevant then it's backported +to B. (With an exception for some patches that document +behaviour that only appears in the maintenance branch, but which has +changed in the development version.) + To report a bug in Perl, use the program I which comes with Perl (if you can't get Perl to work, send mail to the address I or I). Reporting bugs through