From 7f2de2d2ad713e777c0e8d552b0e59a636cc6282 Mon Sep 17 00:00:00 2001 From: Philip Newton Date: Tue, 29 Aug 2000 23:39:14 +0200 Subject: [PATCH] [ID 20000829.023] [PATCH 6868] perlbug@perl.com --> perlbug@perl.org Message-Id: <200008291938.VAA98259@smtp1.nikoma.de> p4raw-id: //depot/perl@6894 --- Configure | 14 +++++++------- INSTALL | 4 ++-- README | 2 +- hints/README.hints | 2 +- hints/bsdos.sh | 2 +- hints/freebsd.sh | 2 +- pod/perl.pod | 2 +- pod/perl56delta.pod | 4 ++-- pod/perlfaq2.pod | 2 +- pod/perllocale.pod | 2 +- pod/perlxs.pod | 2 +- utils/perlbug.PL | 14 +++++++------- 12 files changed, 26 insertions(+), 26 deletions(-) diff --git a/Configure b/Configure index 0661b76..4b5ffc8 100755 --- a/Configure +++ b/Configure @@ -21,7 +21,7 @@ # $Id: Head.U,v 3.0.1.9 1997/02/28 15:02:09 ram Exp $ # # Generated on Mon Aug 28 23:52:13 EET DST 2000 [metaconfig 3.0 PL70] -# (with additional metaconfig patches by perlbug@perl.com) +# (with additional metaconfig patches by perlbug@perl.org) cat >/tmp/c1$$ <&4 @@ -1862,7 +1862,7 @@ Much effort has been expended to ensure that this shell script will run on any Unix system. If despite that it blows up on yours, your best bet is to edit Configure and run it again. If you can't run Configure for some reason, you'll have to generate a config.sh file by hand. Whatever problems you -have, let me (perlbug@perl.com) know how I blew it. +have, let me (perlbug@perl.org) know how I blew it. This installation script affects things in two ways: @@ -2282,7 +2282,7 @@ EOM (cd $src/hints; ls -C *.sh) | $sed 's/\.sh/ /g' >&4 dflt='' : Half the following guesses are probably wrong... If you have better - : tests or hints, please send them to perlbug@perl.com + : tests or hints, please send them to perlbug@perl.org : The metaconfig authors would also appreciate a copy... $test -f /irix && osname=irix $test -f /xenix && osname=sco_xenix @@ -6758,7 +6758,7 @@ case "$shrpdir" in *) $cat >&4 <&4 I did not know that BSD/OS $osvers supports POSIX threads. -Feel free to tell perlbug@perl.com otherwise. +Feel free to tell perlbug@perl.org otherwise. EOM exit 1 ;; diff --git a/hints/freebsd.sh b/hints/freebsd.sh index 7122813..0ba6b61 100644 --- a/hints/freebsd.sh +++ b/hints/freebsd.sh @@ -184,7 +184,7 @@ $define|true|[yY]*) 0*|1*|2.0*|2.1*) cat <&4 I did not know that FreeBSD $osvers supports POSIX threads. -Feel free to tell perlbug@perl.com otherwise. +Feel free to tell perlbug@perl.org otherwise. EOM exit 1 ;; diff --git a/pod/perl.pod b/pod/perl.pod index 895f8d9..fc40d3b 100644 --- a/pod/perl.pod +++ b/pod/perl.pod @@ -317,7 +317,7 @@ affected by wraparound). You may mail your bug reports (be sure to include full configuration information as output by the myconfig program in the perl source -tree, or by C) to perlbug@perl.com . If you've succeeded +tree, or by C) to perlbug@perl.org . If you've succeeded in compiling perl, the B script in the F subdirectory can be used to help mail in a bug report. diff --git a/pod/perl56delta.pod b/pod/perl56delta.pod index 115f88b..63f7060 100644 --- a/pod/perl56delta.pod +++ b/pod/perl56delta.pod @@ -2990,7 +2990,7 @@ Home Page. If you believe you have an unreported bug, please run the B program included with your release. Be sure to trim your bug down to a tiny but sufficient test case. Your bug report, along with the -output of C, will be sent off to perlbug@perl.com to be +output of C, will be sent off to perlbug@perl.org to be analysed by the Perl porting team. =head1 SEE ALSO @@ -3008,6 +3008,6 @@ The F and F files for copyright information. Written by Gurusamy Sarathy >, with many contributions from The Perl Porters. -Send omissions or corrections to >. +Send omissions or corrections to >. =cut diff --git a/pod/perlfaq2.pod b/pod/perlfaq2.pod index d0b92bb..df05091 100644 --- a/pod/perlfaq2.pod +++ b/pod/perlfaq2.pod @@ -462,7 +462,7 @@ See also www.perl.com for updates on tutorials, training, and support. If you are reporting a bug in the perl interpreter or the modules shipped with Perl, use the I program in the Perl distribution or -mail your report to perlbug@perl.com . +mail your report to perlbug@perl.org . If you are posting a bug with a non-standard port (see the answer to "What platforms is Perl available for?"), a binary distribution, or a diff --git a/pod/perllocale.pod b/pod/perllocale.pod index a257e38..3d9a58a 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -947,7 +947,7 @@ In certain systems, the operating system's locale support is broken and cannot be fixed or used by Perl. Such deficiencies can and will result in mysterious hangs and/or Perl core dumps when the C is in effect. When confronted with such a system, -please report in excruciating detail to >, and +please report in excruciating detail to >, and complain to your vendor: bug fixes may exist for these problems in your operating system. Sometimes such bug fixes are called an operating system upgrade. diff --git a/pod/perlxs.pod b/pod/perlxs.pod index c696e19..5e333c0 100644 --- a/pod/perlxs.pod +++ b/pod/perlxs.pod @@ -1636,4 +1636,4 @@ This document covers features supported by C 1.935. Originally written by Dean Roehrich >. -Maintained since 1996 by The Perl Porters >. +Maintained since 1996 by The Perl Porters >. diff --git a/utils/perlbug.PL b/utils/perlbug.PL index ffa3196..6c92254 100644 --- a/utils/perlbug.PL +++ b/utils/perlbug.PL @@ -135,7 +135,7 @@ my $Version = "1.32"; # - Test -b option my( $file, $usefile, $cc, $address, $perlbug, $testaddress, $filename, - $subject, $from, $verbose, $ed, $outfile, $Is_MacOS, $category, $severity, + $subject, $from, $verbose, $ed, $outfile, $Is_MacOS, $category, $severity, $fh, $me, $Is_MSWin32, $Is_VMS, $msg, $body, $andcc, %REP, $ok); my $perl_version = $^V ? sprintf("v%vd", $^V) : $]; @@ -174,9 +174,9 @@ sub ask_for_alternatives { # (category|severity) 'default' => 'low', 'ok' => 'none', 'opts' => [qw(critical high medium low wishlist none)], # zero - }, + }, ); - die "Invalid alternative($name) requested\n" unless grep(/^$name$/, keys %alts); + die "Invalid alternative($name) requested\n" unless grep(/^$name$/, keys %alts); my $alt = ""; if ($ok) { $alt = $alts{$name}{'ok'}; @@ -960,7 +960,7 @@ will be needed. Simply run it, and follow the prompts. If you are unable to run B (most likely because you don't have a working setup to send mail that perlbug recognizes), you may have to -compose your own report, and email it to B. You might +compose your own report, and email it to B. You might find the B<-d> option useful to get summary information in that case. In any case, when reporting a bug, please make sure you have run through @@ -1038,7 +1038,7 @@ definitely be fixed. Use the C program to generate your patches (C is being maintained by the GNU folks as part of the B package, so you should be able to get it from any of the GNU software repositories). If you do submit a patch, the cool-dude counter at -perlbug@perl.com will register you as a savior of the world. Your +perlbug@perl.org will register you as a savior of the world. Your patch may be returned with requests for changes, or requests for more detailed explanations about your fix. @@ -1058,7 +1058,7 @@ B will, amongst other things, ensure your report includes crucial information about your version of perl. If C is unable to mail your report after you have typed it in, you may have to compose the message yourself, add the output produced by C and email -it to B. If, for some reason, you cannot run +it to B. If, for some reason, you cannot run C at all on your system, be sure to include the entire output produced by running C (note the uppercase V). @@ -1085,7 +1085,7 @@ version of perl comes out and your bug is still present. =item B<-a> -Address to send the report to. Defaults to `perlbug@perl.com'. +Address to send the report to. Defaults to `perlbug@perl.org'. =item B<-b> -- 1.8.3.1