[svn-r5347] Change references to mpich2-maint to point to mpich-discuss in

preparation for the move to web-only bug report submission.

README.vin

@@ -12,9 +12,8 @@ with the installation or usage of MPICH2, please send an email to
 mpich-discuss@mcs.anl.gov (you need to subscribe to this list
 (https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss) before
 sending an email). If you have found a bug in MPICH2, we request that
-you report it at our bug tracking system
-(http://wiki.mcs.anl.gov/mpich2/index.php/Creating_New_Bug_Tickets) or
-send an email to mpich2-maint@mcs.anl.gov.
+you report it at our bug tracking system:
+(https://trac.mcs.anl.gov/projects/mpich2/newticket).
 
 This README file should contain enough information to get you started
 with MPICH2. More extensive installation and user guides can be found

configure.in

@@ -3251,7 +3251,7 @@ elif test "$pac_cv_c_max_fp_align" = "eight" ; then
 elif test "$pac_cv_c_max_fp_align" = "sixteen" ; then
     pac_cv_c_fp_align_nr=16
 elif test "$pac_cv_c_max_fp_align" = "largest" ; then
-    AC_MSG_ERROR([Configure detected unsupported structure alignment rules.  Please email mpich2-maint@mcs.anl.gov with complete configure output and information on architecture.])
+    AC_MSG_ERROR([Configure detected unsupported structure alignment rules.])
 fi
 
 if test -n "$pac_cv_c_fp_align_nr" ; then
@@ -4591,7 +4591,7 @@ EOF
     # enabled.
     if test "$enable_f90" = "yes" ; then
         if test "$ADDRESS_KIND" -le 0 -o "$OFFSET_KIND" -le 0 ; then
-	    AC_MSG_ERROR([Unable to determine Fortran integer kinds for MPI types.  If you do not need Fortran 90, add --disable-f90 to the configure options.  If you need Fortran 90, please send the output of configure and the file config.log to mpich2-maint@mcs.anl.gov .])
+	    AC_MSG_ERROR([Unable to determine Fortran integer kinds for MPI types.  If you do not need Fortran 90, add --disable-f90 to the configure options.])
 	    # If the above is converted to a warning, you need to change 
 	    # enable_f90 and remote f90 from the bindings
 	    enable_f90=no

doc/installguide/install.tex.vin

@@ -105,7 +105,7 @@ run MPI applications.  Some particular features are different
 if you have system administration privileges (can become ``root'' on a
 Unix system), and these are explained here.  It is not necessary to have
 such privileges to build and install MPICH2.  In the event of problems,
-send mail to \texttt{mpich2-maint@mcs.anl.gov}.  Once MPICH2 is
+send mail to \texttt{mpich-discuss@mcs.anl.gov}.  Once MPICH2 is
 installed, details on how to run MPI jobs are covered in the \emph{MPICH2
 User's Guide}, found in this same \texttt{doc} subdirectory.
 
@@ -209,7 +209,7 @@ where the \texttt{$\backslash$} means that this is really one line.  (On
 instead of \verb+|& tee c.txt+).  Other configure options are
 described below.  Check the \texttt{c.txt} file to make sure
 everything went well.  Problems should be self-explanatory, but if not,
-send \texttt{c.txt} to \texttt{mpich2-maint@mcs.anl.gov}.
+send \texttt{c.txt} to \texttt{mpich-discuss@mcs.anl.gov}.
 The file \texttt{config.log} is created by \texttt{configure} and
 contains a record of the tests that \texttt{configure} performed.  It
 is normal for some tests recorded in \texttt{config.log} to fail.  
@@ -230,7 +230,7 @@ do a \texttt{make clean} and then run make again with \texttt{VERBOSE=1}
     make VERBOSE=1 2>&1 | tee m.txt   (for bash and sh)
 \end{verbatim}
 and then send \texttt{m.txt} and \texttt{c.txt} to 
-\texttt{mpich2-maint@mcs.anl.gov}.
+\texttt{mpich-discuss@mcs.anl.gov}.
 
 \item
 Install the MPICH2 commands:

doc/mansrc/manpage.txt

@@ -76,6 +76,6 @@ Files:
 Contact:
 
 MPI-specific suggestions and bug reports should
-be sent to 'mpich2-maint@mcs.anl.gov'.
+be sent to 'mpich-discuss@mcs.anl.gov'.
 
 D*/

doc/mpiman.def

@@ -1,6 +1,6 @@
 hdef mpich 0 '<TT>MPICH</TT>'
 hdef Mpich 0 '<TT>MPICH</TT>'
-hdef mpibug 0 '<A HREF="mailto:mpich2-maint@mcs.anl.gov">mpich2-maint@mcs.anl.gov</A>'
+hdef mpibug 0 '<A HREF="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</A>'
 hdef url 1 '<A HREF="#1">#1</A>'
 hdef urlname 1 '<A HREF="#1">#1</A>'
 hdef mpifile 1 '<TT>/usr/local/mpich2-1.0.3/#1</TT>'

doc/mpiman.sty

@@ -9,7 +9,7 @@
 % This should really use #1, but we want the text version in the Postscript
 % document
 \newcommand{\AURL}[2]{\url{#2}}
-\newcommand{\mpibug}{\AURL{mailto:mpich2-maint@mcs.anl.gov}{mpich2-maint@mcs.anl.gov}}
+\newcommand{\mpibug}{\AURL{mailto:mpich-discuss@mcs.anl.gov}{mpich-discuss@mcs.anl.gov}}
 %\newcommand{\mpich}{MPICH}
 %
 % Fix this using hyphenation?

doc/pmi/paper.tex

@@ -640,7 +640,7 @@ as if one had specified
 \begin{verbatim}
      configure --with-pmi=simple --with-pm=mpd
 \end{verbatim}
-Please send questions and comments to mpich2-maint@mcs.anl.gov.
+Please send questions and comments to mpich-discuss@mcs.anl.gov.
 
 %\appendix
 %\section{Wire Protocol for the Simple PMI Implementation}