From: Philip Newton Date: Fri, 30 Mar 2001 19:06:57 +0000 (+0200) Subject: [DOC PATCH bleadperl] Two nits in perlhack.pod X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=f18956b7b7075f4d5c8a71544673eedaab733e30;p=p5sagit%2Fp5-mst-13.2.git [DOC PATCH bleadperl] Two nits in perlhack.pod Message-ID: <3AC4D951.14815.1AC7068@localhost> p4raw-id: //depot/perl@9475 --- diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 5a8f61e..cec4281 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -410,7 +410,7 @@ the current source tree (i.e. perl@7582.tar.gz), which will be an excellent point to start with when choosing to use the 'rsync the patches' scheme. Starting with perl@7582, which means a set of source files on which the latest applied patch is number 7582, you apply all -succeeding patches available from than on (7583, 7584, ...). +succeeding patches available from then on (7583, 7584, ...). You can use the patches later as a kind of search archive. @@ -486,7 +486,7 @@ Your patch should update the documentation and test suite. 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 +I or I). Reporting bugs through I feeds into the automated bug-tracking system, access to which is provided through the web at I. It often pays to check the archives of the perl5-porters mailing list to