Update references to the mailing list.

[simgrid.git] / doc / doxygen / outcomes_vizu.doc

diff --git a/doc/doxygen/outcomes_vizu.doc b/doc/doxygen/outcomes_vizu.doc
index 351a7b2..f97248b 100644 (file)
--- a/doc/doxygen/outcomes_vizu.doc
+++ b/doc/doxygen/outcomes_vizu.doc
@@ -2,7 +2,7 @@
 
 SimGrid comes with an extensive support to trace and register what
 happens during the simulation, so that it can be either visualized or
 
 SimGrid comes with an extensive support to trace and register what
 happens during the simulation, so that it can be either visualized or

-statistically analysed after the simulation. 
+statistically analysed after the simulation.

 
 This tracing is widely used to observe and understand the behavior of
 parallel applications and distributed algorithms. Usually, this is
 
 This tracing is widely used to observe and understand the behavior of
 parallel applications and distributed algorithms. Usually, this is


@@ -438,7 +438,7 @@ several options to analyze this trace file:
   SimGrid User::Visualization 101 tutorial.
 
 - Ask for help on the <a
   SimGrid User::Visualization 101 tutorial.
 
 - Ask for help on the <a

-  href="mailto:simgrid-user@lists.gforge.inria.fr">simgrid-user@lists.gforge.inria.fr</a>
+  href="mailto:simgrid-community@inria.fr">simgrid-community@inria.fr</a>

   mailing list, giving us a detailed explanation on what your
   simulator does and what kind of information you want to trace. You
   can also check the <a
   mailing list, giving us a detailed explanation on what your
   simulator does and what kind of information you want to trace. You
   can also check the <a