Change 28699 by [EMAIL PROTECTED] on 2006/08/13 07:51:46
Fix a couple URLs in perlhack
Affected files ...
... //depot/perl/pod/perlhack.pod#118 edit
Differences ...
==== //depot/perl/pod/perlhack.pod#118 (text) ====
Index: perl/pod/perlhack.pod
--- perl/pod/perlhack.pod#117~28698~ 2006-08-12 05:53:32.000000000 -0700
+++ perl/pod/perlhack.pod 2006-08-13 00:51:46.000000000 -0700
@@ -450,7 +450,7 @@
I<see> that the community efforts really work. So after each of his
sync points, you are to 'make test' to check if everything is still
in working order. If it is, you do 'make ok', which will send an OK
-report to [EMAIL PROTECTED] (If you do not have access to a mailer
+report to I<[EMAIL PROTECTED]>. (If you do not have access to a mailer
from the system you just finished successfully 'make test', you can
do 'make okfile', which creates the file C<perl.ok>, which you can
than take to your favourite mailer and mail yourself).
@@ -570,22 +570,17 @@
=head2 Perlbug administration
-There is a single remote administrative interface for modifying bug status,
-category, open issues etc. using the B<RT> I<bugtracker> system, maintained
-by I<Robert Spier>. Become an administrator, and close any bugs you can get
+There is a single remote administrative interface for modifying bug status,
+category, open issues etc. using the B<RT> bugtracker system, maintained
+by Robert Spier. Become an administrator, and close any bugs you can get
your sticky mitts on:
- http://rt.perl.org
-
-The bugtracker mechanism for B<perl5> bugs in particular is at:
-
- http://bugs6.perl.org/perlbug
+ http://rt.perl.org/rt3/
To email the bug system administrators:
"perlbug-admin" <[EMAIL PROTECTED]>
-
=head2 Submitting patches
Always submit patches to I<[email protected]>. If you're
@@ -620,7 +615,7 @@
Perl (if you can't get Perl to work, send mail to the address
I<[EMAIL PROTECTED]> or I<[EMAIL PROTECTED]>). Reporting bugs through
I<perlbug> feeds into the automated bug-tracking system, access to
-which is provided through the web at http://bugs.perl.org/ . It
+which is provided through the web at http://rt.perl.org/rt3/ . It
often pays to check the archives of the perl5-porters mailing list to
see whether the bug you're reporting has been reported before, and if
so whether it was considered a bug. See above for the location of
@@ -628,8 +623,8 @@
The CPAN testers ( http://testers.cpan.org/ ) are a group of
volunteers who test CPAN modules on a variety of platforms. Perl
-Smokers ( http://archives.develooper.com/[email protected]/ )
-automatically tests Perl source releases on platforms with various
+Smokers ( http://www.nntp.perl.org/group/perl.daily-build )
+automatically test Perl source releases on platforms with various
configurations. Both efforts welcome volunteers.
It's a good idea to read and lurk for a while before chipping in.
@@ -679,11 +674,9 @@
=item The perl5-porters FAQ
-This should be available from http://simon-cozens.org/writings/p5p-faq ;
-alternatively, you can get the FAQ emailed to you by sending mail to
-C<[EMAIL PROTECTED]>. It contains hints on reading perl5-porters,
-information on how perl5-porters works and how Perl development in general
-works.
+This should be available from http://dev.perl.org/perl5/docs/p5p-faq.html .
+It contains hints on reading perl5-porters, information on how
+perl5-porters works and how Perl development in general works.
=back
@@ -2561,7 +2554,7 @@
=item *
-That no other fields exist besides the ones you know of know of
+That no other fields exist besides the ones you know of
=item *
End of Patch.
