This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "MPICH primary repository". The branch, master has been updated via 155b82af636e7f38fff0c496f89bd5da83273c71 (commit) from e77cac8e420b86ac993f85acffa40d1dad3d1c7e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.mpich.org/mpich.git/commitdiff/155b82af636e7f38fff0c496f89bd5da83... commit 155b82af636e7f38fff0c496f89bd5da83273c71 Author: Pavan Balaji <[email protected]> Date: Thu Jun 13 16:54:30 2013 -0500 Fixes #1882. Remove old mcs.anl.gov references. diff --git a/README.vin b/README.vin index a13b933..c173cd7 100644 --- a/README.vin +++ b/README.vin @@ -12,9 +12,8 @@ in the doc/installguide/install.pdf and doc/userguide/user.pdf files respectively. Additional information regarding the contents of the release can be found in the CHANGES file in the top-level directory, and in the RELEASE_NOTES file, where certain restrictions are -detailed. Finally, the MPICH web site, -http://www.mcs.anl.gov/research/projects/mpich, contains information -on bug fixes and new releases. +detailed. Finally, the MPICH web site, http://www.mpich.org, contains +information on bug fixes and new releases. 1. Getting Started @@ -235,15 +234,15 @@ see if the problem you are facing has a simple solution. Many common problems and their solutions are listed here. 2. If you cannot find an answer on the FAQ page, look through previous -email threads on the mpich-discuss mailing list archive -(http://lists.mcs.anl.gov/pipermail/mpich-discuss/). It is likely +email threads on the [email protected] mailing list archive +(https://lists.mpich.org/mailman/listinfo/discuss). It is likely someone else had a similar problem, which has already been resolved before. 3. If neither of the above steps work, please send an email to [email protected]. You need to subscribe to this list -(https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss) before -sending an email. [email protected]. You need to subscribe to this list +(https://lists.mpich.org/mailman/listinfo/discuss) before sending an +email. Your email should contain the following files. ONCE AGAIN, PLEASE COMPRESS BEFORE SENDING, AS THE FILES CAN BE LARGE. Note that, @@ -274,9 +273,9 @@ application or benchmark and send that along in your bug report. 4. If you have found a bug in MPICH, we request that you report it at our bug tracking system: -(https://trac.mpich.org/projects/mpich/newticket). Even if you -believe you have found a bug, we recommend you sending an email to [email protected] first. +(https://trac.mpich.org/projects/mpich/newticket). Even if you believe +you have found a bug, we recommend you sending an email to [email protected] first. ------------------------------------------------------------------------- @@ -860,8 +859,7 @@ Here are the instructions for setting up MPICH on a Windows machine: (b) Checkout mpich: Bring up a command prompt. - (replace "yourname" with your MCS login name): - svn co https://svn.mcs.anl.gov/repos/mpi/mpich2/trunk mpich + git clone git.mpich.org:mpich (c) Generate *.h.in ----------------------------------------------------------------------- Summary of changes: README.vin | 24 +++++++++++------------- 1 files changed, 11 insertions(+), 13 deletions(-) hooks/post-receive -- MPICH primary repository