diff options
| -rwxr-xr-x | Configure | 14 | ||||
| -rw-r--r-- | INSTALL | 4 | ||||
| -rw-r--r-- | README | 2 | ||||
| -rw-r--r-- | hints/README.hints | 2 | ||||
| -rw-r--r-- | hints/bsdos.sh | 2 | ||||
| -rw-r--r-- | hints/freebsd.sh | 2 | ||||
| -rw-r--r-- | pod/perl.pod | 2 | ||||
| -rw-r--r-- | pod/perl56delta.pod | 4 | ||||
| -rw-r--r-- | pod/perlfaq2.pod | 2 | ||||
| -rw-r--r-- | pod/perllocale.pod | 2 | ||||
| -rw-r--r-- | pod/perlxs.pod | 2 | ||||
| -rw-r--r-- | utils/perlbug.PL | 14 |
12 files changed, 26 insertions, 26 deletions
@@ -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$$ <<EOF ARGGGHHHH!!!!! @@ -1062,7 +1062,7 @@ case "$sh" in $me: Fatal Error: I can't find a Bourne Shell anywhere. Usually it's in /bin/sh. How did you even get this far? -Please contact me (Perl Maintainers) at perlbug@perl.com and +Please contact me (Perl Maintainers) at perlbug@perl.org and we'll try to straighten this all out. EOM exit 1 @@ -1603,7 +1603,7 @@ THIS PACKAGE SEEMS TO BE INCOMPLETE. You have the option of continuing the configuration process, despite the distinct possibility that your kit is damaged, by typing 'y'es. If you do, don't blame me if something goes wrong. I advise you to type 'n'o -and contact the author (perlbug@perl.com). +and contact the author (perlbug@perl.org). EOM echo $n "Continue? [n] $c" >&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 <<EOM WARNING: Use of the shrpdir variable for the installation location of the shared $libperl is not supported. It was never documented and -will not work in this version. Let me (perlbug@perl.com) +will not work in this version. Let me (perlbug@perl.org) know of any problems this may cause. EOM @@ -7342,7 +7342,7 @@ $cat <<EOM If you or somebody else will be maintaining perl at your site, please fill in the correct e-mail address here so that they may be contacted if necessary. Currently, the "perlbug" program included with perl -will send mail to this address in addition to perlbug@perl.com. You may +will send mail to this address in addition to perlbug@perl.org. You may enter "none" for no administrator. EOM @@ -168,7 +168,7 @@ run, you may have to run it on a platform where GCC is available, and move the sources back to the platform without GCC. If you succeed in automatically converting the sources to a K&R compatible -form, be sure to email perlbug@perl.com to let us know the steps you +form, be sure to email perlbug@perl.org to let us know the steps you followed. This will enable us to officially support this option. =back @@ -2010,7 +2010,7 @@ available in TeX format. Type If you have difficulty building perl, and none of the advice in this file helps, and careful reading of the error message and the relevant manual pages on your system doesn't help either, then you should send a message -to either the comp.lang.perl.misc newsgroup or to perlbug@perl.com with +to either the comp.lang.perl.misc newsgroup or to perlbug@perl.org with an accurate description of your problem. Please include the output of the ./myconfig shell script that comes with @@ -72,7 +72,7 @@ corresponding README. 2) Read the manual entries before running perl. 3) IMPORTANT! Help save the world! Communicate any problems and suggested -patches to perlbug@perl.com so we can keep the world in sync. +patches to perlbug@perl.org so we can keep the world in sync. If you have a problem, there's someone else out there who either has had or will have the same problem. It's usually helpful if you send the output of the "myconfig" script in the main perl directory. diff --git a/hints/README.hints b/hints/README.hints index 5f23b29c2c..0666771952 100644 --- a/hints/README.hints +++ b/hints/README.hints @@ -9,7 +9,7 @@ can't or doesn't guess properly. Most of these hint files have been tested with at least some version of perl5, but some are still left over from perl4. -Please send any problems or suggested changes to perlbug@perl.com. +Please send any problems or suggested changes to perlbug@perl.org. =head1 Hint file naming convention. diff --git a/hints/bsdos.sh b/hints/bsdos.sh index 1d1d823b03..58755434a3 100644 --- a/hints/bsdos.sh +++ b/hints/bsdos.sh @@ -121,7 +121,7 @@ $define|true|[yY]*) *) cat <<EOM >&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 712281367e..0ba6b6190e 100644 --- a/hints/freebsd.sh +++ b/hints/freebsd.sh @@ -184,7 +184,7 @@ $define|true|[yY]*) 0*|1*|2.0*|2.1*) cat <<EOM >&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 895f8d981a..fc40d3b33a 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<perl -V>) to perlbug@perl.com . If you've succeeded +tree, or by C<perl -V>) to perlbug@perl.org . If you've succeeded in compiling perl, the B<perlbug> script in the F<utils/> subdirectory can be used to help mail in a bug report. diff --git a/pod/perl56delta.pod b/pod/perl56delta.pod index 115f88b754..63f7060d87 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<perlbug> 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<perl -V>, will be sent off to perlbug@perl.com to be +output of C<perl -V>, 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<Artistic> and F<Copying> files for copyright information. Written by Gurusamy Sarathy <F<gsar@activestate.com>>, with many contributions from The Perl Porters. -Send omissions or corrections to <F<perlbug@perl.com>>. +Send omissions or corrections to <F<perlbug@perl.org>>. =cut diff --git a/pod/perlfaq2.pod b/pod/perlfaq2.pod index d0b92bb941..df05091e06 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<perlbug> 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 a257e380c0..3d9a58a007 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<use locale> is in effect. When confronted with such a system, -please report in excruciating detail to <F<perlbug@perl.com>>, and +please report in excruciating detail to <F<perlbug@perl.org>>, 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 c696e19d16..5e333c088d 100644 --- a/pod/perlxs.pod +++ b/pod/perlxs.pod @@ -1636,4 +1636,4 @@ This document covers features supported by C<xsubpp> 1.935. Originally written by Dean Roehrich <F<roehrich@cray.com>>. -Maintained since 1996 by The Perl Porters <F<perlbug@perl.com>>. +Maintained since 1996 by The Perl Porters <F<perlbug@perl.org>>. diff --git a/utils/perlbug.PL b/utils/perlbug.PL index ffa31964ab..6c92254d81 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<perlbug> (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<perlbug@perl.com>. You might +compose your own report, and email it to B<perlbug@perl.org>. 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<diff> program to generate your patches (C<diff> is being maintained by the GNU folks as part of the B<diffutils> 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<perlbug> will, amongst other things, ensure your report includes crucial information about your version of perl. If C<perlbug> 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<perlbug -d> and email -it to B<perlbug@perl.com>. If, for some reason, you cannot run +it to B<perlbug@perl.org>. If, for some reason, you cannot run C<perlbug> at all on your system, be sure to include the entire output produced by running C<perl -V> (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> |