Update perlbug email address to perlbug@perl.org

git-svn-id: http://perl5005.googlecode.com/svn/trunk@9 e77bdc90-ac31-0410-a84a-cbf48518d05f

12 files changed, 29 insertions, 22 deletions

diff --git a/Changes b/Changes
index 2de39e0ca6..44b4763d3b 100644
--- a/Changes
+++ b/Changes
@@ -80,6 +80,13 @@ Version 5.005_04        Fourth maintenance release of 5.005
 
 
 ____________________________________________________________________________
+[      ] By: acme                                  on 2007/06/10  13:05:58
+        Log: Update perlbug email address to perlbug@perl.org
+     Branch: maint-5.005/perl
+           ! utils/perlbug.PL pod/perllocale.pod pod/perlfaq2.pod 
+             pod/perl.pod hints/README.hints configure.com README.win32
+             README.vms README INSTALL Configure
+____________________________________________________________________________
 [      ] By: acme                                  on 2007/06/10  12:52:18
         Log: Tests in t/lib/db-recno.t fail on both of these machines.
              The attached patch fixes this by making sure the file DB_File
diff --git a/Configure b/Configure
index 3991c33002..1f48a50d1f 100755
--- a/Configure
+++ b/Configure
@@ -901,7 +901,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 perlbug@perl.com and we'll try to straighten this all out.
+Please contact perlbug@perl.org and we'll try to straighten this all out.
 EOM
 	exit 1
 	;;
@@ -1369,7 +1369,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 then contact perlbug@perl.com.
+and then contact perlbug@perl.org.
 
 EOM
 		echo $n "Continue? [n] $c" >&4
@@ -1594,7 +1594,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 perlbug@perl.com know how I blew it.
+have, let perlbug@perl.org know how I blew it.
 
 This installation script affects things in two ways:
 
@@ -1961,7 +1961,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
@@ -2461,7 +2461,7 @@ case "$usethreads" in
 	*)
 	        cat >&4 <<EOM
 $osname is not known to support threads.
-Please let perlbug@perl.com know how to do that.
+Please let perlbug@perl.org know how to do that.
 
 Cannot continue, aborting.
 EOM
@@ -5204,7 +5204,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 perlbug@perl.com
+will not work in this version.  Let perlbug@perl.org
 know of any problems this may cause.
 
 EOM
@@ -5809,7 +5809,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
diff --git a/INSTALL b/INSTALL
index 7f8609f885..80c42c6d4d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1021,7 +1021,7 @@ If you can't compile successfully, try some of the following ideas.
 If none of them help, and careful reading of the error message and
 the relevant manual pages on your system doesn't help, you can
 send a message to either the comp.lang.perl.misc newsgroup or to
-perlbug@perl.com with an accurate description of your problem.
+perlbug@perl.org with an accurate description of your problem.
 See L<"Reporting Problems"> below.
 
 =over 4
@@ -1626,7 +1626,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
diff --git a/README b/README
index 18f1104be1..68611bf261 100644
--- a/README
+++ b/README
@@ -76,7 +76,7 @@ or if you have any problems building.)
 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/README.vms b/README.vms
index e2c0e0832e..82e1f36f84 100644
--- a/README.vms
+++ b/README.vms
@@ -334,7 +334,7 @@ If you come across what you think might be a bug in Perl, please report
 it. There's a script in PERL_ROOT:[UTILS], perlbug, that walks you through
 the process of creating a bug report. This script includes details of your
 installation, and is very handy. Completed bug reports should go to
-perlbug@perl.com.
+perlbug@perl.org.
 
 * Gotchas to watch out for
 
diff --git a/README.win32 b/README.win32
index 69004adb5d..f6fe64c2d2 100644
--- a/README.win32
+++ b/README.win32
@@ -716,7 +716,7 @@ still only provides DOS semantics (read "warts") for globbing.
 =back

 

 Please send detailed descriptions of any problems and solutions that 

-you may find to <F<perlbug@perl.com>>, along with the output produced

+you may find to <F<perlbug@perl.org>>, along with the output produced

 by C<perl -V>.

 

 =head1 AUTHORS

diff --git a/configure.com b/configure.com
index d51793abe8..5831599228 100644
--- a/configure.com
+++ b/configure.com
@@ -1596,7 +1596,7 @@ $ THEN TYPE SYS$INPUT:
 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.
 $ ENDIF
 $ dflt = "''cf_email'"
diff --git a/hints/README.hints b/hints/README.hints
index e36bd6d1dd..fee7d6c125 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.
 
 Hint file naming convention:   Each hint file name should have only
 one '.'.  (This is for portability to non-unix file systems.)  Names
diff --git a/pod/perl.pod b/pod/perl.pod
index 9aa753d55d..2e9311c56e 100644
--- a/pod/perl.pod
+++ b/pod/perl.pod
@@ -311,7 +311,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 <F<perlbug@perl.com>>.
+or by C<perl -V>) to <F<perlbug@perl.org>>.
 If you've succeeded in compiling perl, the perlbug script in the utils/
 subdirectory can be used to help mail in a bug report.
 
diff --git a/pod/perlfaq2.pod b/pod/perlfaq2.pod
index 32970af58a..4809b2b8d1 100644
--- a/pod/perlfaq2.pod
+++ b/pod/perlfaq2.pod
@@ -416,7 +416,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 08b50e0d12..9387d083a9 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -945,7 +945,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/utils/perlbug.PL b/utils/perlbug.PL
index 6f8758919f..378e7f723d 100644
--- a/utils/perlbug.PL
+++ b/utils/perlbug.PL
@@ -163,7 +163,7 @@ sub Init {
     # -------- Configuration ---------
 
     # perlbug address
-    $perlbug = 'perlbug@perl.com';
+    $perlbug = 'perlbug@perl.org';
 
     # Test address
     $testaddress = 'perlbug-test@perl.com';
@@ -870,7 +870,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
@@ -948,7 +948,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.
 
@@ -968,7 +968,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).
 
@@ -995,7 +995,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>