From 8d6134660c63d662391631e888a34b24b25128a7 Mon Sep 17 00:00:00 2001
From: Wolfgang Bangerth <bangerth@math.tamu.edu>
Date: Sat, 23 Jan 2016 18:37:12 -0600
Subject: [PATCH] Remove a comment that's no longer correct.

In fact, remove the entire section since there is a link to an extensive
documentation module just a couple of lines further down.
---
 include/deal.II/fe/fe_values.h | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/include/deal.II/fe/fe_values.h b/include/deal.II/fe/fe_values.h
index 495822167b..cac013f202 100644
--- a/include/deal.II/fe/fe_values.h
+++ b/include/deal.II/fe/fe_values.h
@@ -1421,19 +1421,6 @@ namespace internal
  * </ul>
  *
  *
- * <h3>UpdateFlags</h3>
- *
- * The UpdateFlags object handed to the constructor is used to determine which
- * of the data fields to compute. This way, it is possible to avoid expensive
- * computations of useless derivatives.  In the beginning, these flags are
- * processed through the functions Mapping::update_once(),
- * Mapping::update_each(), FiniteElement::update_once()
- * FiniteElement::update_each(). All the results are bit-wise or'd and
- * determine the fields actually computed. This enables Mapping and
- * FiniteElement to schedule auxiliary data fields for updating. Still, it is
- * recommended to give <b>all</b> needed update flags to FEValues.
- *
- *
  * <h3>Internals about the implementation</h3>
  *
  * The mechanisms by which this class work are discussed on the page on
-- 
2.39.5