From 192a27858b07fa43afdfa367021dbb4369c00877 Mon Sep 17 00:00:00 2001
From: bangerth <bangerth@0785d39b-7218-0410-832d-ea1e28bc413d>
Date: Sat, 8 Oct 2011 23:17:21 +0000
Subject: [PATCH] Do not link to the deleted step-37.

git-svn-id: https://svn.dealii.org/branches/releases/Branch-7-1@24582 0785d39b-7218-0410-832d-ea1e28bc413d
---
 deal.II/doc/doxygen/headers/multithreading.h | 30 ++++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/deal.II/doc/doxygen/headers/multithreading.h b/deal.II/doc/doxygen/headers/multithreading.h
index 194308e9e1..44643c29ad 100644
--- a/deal.II/doc/doxygen/headers/multithreading.h
+++ b/deal.II/doc/doxygen/headers/multithreading.h
@@ -34,8 +34,8 @@
  * namespace. The MultithreadInfo class allows to query certain
  * properties of the system, such as the number of CPUs. These
  * facilities for %parallel computing are described in the
- * following. The step-9, step-13, step-14, step-32, step-35 and
- * step-37 tutorial programs also show their use in practice, with the
+ * following. The step-9, step-13, step-14, step-32 and step-35
+ * tutorial programs also show their use in practice, with the
  * ones starting with step-32 using a more modern style of doing
  * things in which essentially we describe <i>what</i> can be done in
  * %parallel, while the older tutorial programs describe <i>how</i>
@@ -916,11 +916,11 @@
 		:
 		fe_values (fe, quadrature, update_flags)
        {}
-     
+
      ScratchData (const ScratchData &scratch)
 		:
-		fe_values (scratch.fe_values.get_fe(), 
-		           scratch.fe_values.get_quadrature(), 
+		fe_values (scratch.fe_values.get_fe(),
+		           scratch.fe_values.get_quadrature(),
 		           scratch.fe_values.get_update_flags())
        {}
    }
@@ -936,13 +936,13 @@
      ...
    }
  * @endcode
- *   Just as for the <code>PerTaskData</code> structure, we will create a 
+ *   Just as for the <code>PerTaskData</code> structure, we will create a
  *   sample <code>ScratchData</code> object and pass it to the work stream
- *   object, which will replicate it as many times as necessary. For this 
- *   to work <code>ScratchData</code> structures need to copyable. Since FEValues 
- *   objects are rather complex and cannot be copied implicitly, we provided 
- *   our own copy constructor for the <code>ScratchData</code> structure. 
- * 
+ *   object, which will replicate it as many times as necessary. For this
+ *   to work <code>ScratchData</code> structures need to copyable. Since FEValues
+ *   objects are rather complex and cannot be copied implicitly, we provided
+ *   our own copy constructor for the <code>ScratchData</code> structure.
+ *
  *   The same approach, putting things into the <code>ScratchData</code>
  *   data structure, should be used for everything that is expensive to
  *   construct. This holds, in particular, for everything that needs to
@@ -974,12 +974,12 @@
 		rhs_values (quadrature.size()),
 		fe_values (fe, quadrature, update_flags)
        {}
-       
+
       ScratchData (const ScratchData &scratch)
 		:
 		rhs_values (scratch.rhs_values),
-		fe_values (scratch.fe_values.get_fe(), 
-		           scratch.fe_values.get_quadrature(), 
+		fe_values (scratch.fe_values.get_fe(),
+		           scratch.fe_values.get_quadrature(),
 		           scratch.fe_values.get_update_flags())
        {}
    }
@@ -1068,7 +1068,7 @@
  * in at the positions indicated by <code>std_cxx1x::_1, std_cxx1x::_2</code> and <code>std_cxx1x::_3</code>.
  *
  * To see the WorkStream class used in practice on tasks like the ones
- * outlined above, take a look at the step-32, step-35 or step-37
+ * outlined above, take a look at the step-32 or step-35
  * tutorial programs.
  *
  *
-- 
2.39.5