From: David Wells <wellsd2@rpi.edu>
Date: Wed, 18 May 2016 03:51:00 +0000 (-0400)
Subject: Fix a bunch of old google code links.
X-Git-Tag: v8.5.0-rc1~1030^2
X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ee8671b216c182e450b6df35b1a579409d61d01a;p=dealii.git

Fix a bunch of old google code links.
---

diff --git a/doc/users/cmake.html b/doc/users/cmake.html
index d5431c14f4..6ad040c450 100644
--- a/doc/users/cmake.html
+++ b/doc/users/cmake.html
@@ -344,8 +344,9 @@ $ cmake .
 $ cmake -G"Eclipse CDT4 - Unix Makefiles" [...]
 </pre>
       and load up the build directory as a project directly into Eclipse.
-      Have a look at the <a href="https://code.google.com/p/dealii/w/list"
-      target="_top">Wiki</a> for more information.
+      Have a look at
+      the <a href="https://github.com/dealii/dealii/wiki/Eclipse">Wiki's
+      Eclipse page</a> for more information.
     </p>
 
     <p>
diff --git a/examples/step-1/doc/intro.dox b/examples/step-1/doc/intro.dox
index 14dbb8054f..1834ff4d59 100644
--- a/examples/step-1/doc/intro.dox
+++ b/examples/step-1/doc/intro.dox
@@ -165,12 +165,11 @@ lines. Remember: Producing software is not the same as just writing code.
 To make your life easier on this journey let us point to three resources that
 are worthwhile browsing through before you start any large-scale programming:
 
-- The <a
-  href="http://code.google.com/p/dealii/wiki/FrequentlyAskedQuestions">deal.II
-  Frequently Asked Questions</a>: This page has a good number of questions
-  that pertain to particular aspects of deal.II, but also to more general
-  questions such as "How do I debug scientific computing codes?" or "Can I
-  train myself to write code that has fewer bugs?".
+- <a href="https://github.com/dealii/dealii/wiki/Frequently-Asked-Questions">
+  The deal.II FAQ</a> has a good number of answers to questions about
+  particular aspects of deal.II, but also to more general questions such as "How
+  do I debug scientific computing codes?" or "Can I train myself to write code
+  that has fewer bugs?".
 
 - The <a href="http://software-carpentry.org/">Software Carpentry project</a>
   that provides introductions to many topics that are important to dealing
diff --git a/include/deal.II/grid/grid_in.h b/include/deal.II/grid/grid_in.h
index 72e99ee9c2..7d8a2db759 100644
--- a/include/deal.II/grid/grid_in.h
+++ b/include/deal.II/grid/grid_in.h
@@ -45,8 +45,8 @@ template <int dim> struct CellData;
  * meshes, the functions in this class can only read meshes that consist
  * exclusively of such cells. If you absolutely need to work with a mesh that
  * uses triangles or tetrahedra, then your only option is to convert the mesh
- * to quadrilaterals and hexahedra. A tool that can do this is tethex, see
- * http://code.google.com/p/tethex/wiki/Tethex .
+ * to quadrilaterals and hexahedra. A tool that can do this is tethex,
+ * available <a href="https://github.com/martemyev/tethex">here</a>.
  *
  * The mesh you read will form the coarsest level of a @p Triangulation
  * object. As such, it must not contain hanging nodes or other forms of
@@ -207,8 +207,9 @@ template <int dim> struct CellData;
  * <li> <tt>Cubit</tt> format: deal.II doesn't directly support importing from
  * Cubit at this time. However, Cubit can export in UCD format using a simple
  * plug-in, and the resulting UCD file can then be read by this class. The
- * plug-in script can be found on the deal.II wiki page,
- * http://code.google.com/p/dealii/wiki/MeshInputAndOutput .
+ * plug-in script can be found on the deal.II wiki page under
+ * <a href="https://github.com/dealii/dealii/wiki/Mesh-Input-And-Output">Mesh
+ * Input and Output</a>.
  *
  * Alternatively, Cubit can generate ABAQUS files that can be read in via the
  * read_abaqus() function. This may be a better option for geometries with