[2.2.x] Used extlinks for Django's source code.

Backport of a68c029e224cebe540da7447dbbd27993b4aa793 from master.

4 files changed, 6 insertions, 14 deletions

diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt
index dfffb61ec6..f9126cc9e2 100644
--- a/docs/ref/contrib/flatpages.txt
+++ b/docs/ref/contrib/flatpages.txt
@@ -213,11 +213,9 @@ Via the Python API
 
     Flatpages are represented by a standard
     :doc:`Django model </topics/db/models>`,
-    which lives in `django/contrib/flatpages/models.py`_. You can access
+    which lives in :source:`django/contrib/flatpages/models.py`. You can access
     flatpage objects via the :doc:`Django database API </topics/db/queries>`.
 
-.. _django/contrib/flatpages/models.py: https://github.com/django/django/blob/master/django/contrib/flatpages/models.py
-
 .. currentmodule:: django.contrib.flatpages
 
 .. admonition:: Check for duplicate flatpage URLs.
diff --git a/docs/ref/contrib/gis/db-api.txt b/docs/ref/contrib/gis/db-api.txt
index b70ae11067..d5ddb2564c 100644
--- a/docs/ref/contrib/gis/db-api.txt
+++ b/docs/ref/contrib/gis/db-api.txt
@@ -268,8 +268,8 @@ to be in the units of the field.
     in your field definition.
 
 For example, let's say we have a ``SouthTexasCity`` model (from the
-`GeoDjango distance tests`__ ) on a *projected* coordinate system valid for cities
-in southern Texas::
+:source:`GeoDjango distance tests <tests/gis_tests/distapp/models.py>` ) on a
+*projected* coordinate system valid for cities in southern Texas::
 
     from django.contrib.gis.db import models
 
@@ -303,8 +303,6 @@ both. To specify the band index of a raster input on the right hand side, a
 Where the band with index 2 (the third band) of the raster ``rst`` would be
 used for the lookup.
 
-__ https://github.com/django/django/blob/master/tests/gis_tests/distapp/models.py
-
 .. _compatibility-table:
 
 Compatibility Tables
diff --git a/docs/ref/contrib/redirects.txt b/docs/ref/contrib/redirects.txt
index 15417d6f30..a37aee8711 100644
--- a/docs/ref/contrib/redirects.txt
+++ b/docs/ref/contrib/redirects.txt
@@ -72,10 +72,8 @@ Via the Python API
 .. class:: models.Redirect
 
     Redirects are represented by a standard :doc:`Django model </topics/db/models>`,
-    which lives in `django/contrib/redirects/models.py`_. You can access redirect
-    objects via the :doc:`Django database API </topics/db/queries>`.
-
-.. _django/contrib/redirects/models.py: https://github.com/django/django/blob/master/django/contrib/redirects/models.py
+    which lives in :source:`django/contrib/redirects/models.py`. You can access
+    redirect objects via the :doc:`Django database API </topics/db/queries>`.
 
 Middleware
 ==========
diff --git a/docs/ref/contrib/syndication.txt b/docs/ref/contrib/syndication.txt
index ab3fcba5d4..d79db5a94a 100644
--- a/docs/ref/contrib/syndication.txt
+++ b/docs/ref/contrib/syndication.txt
@@ -892,7 +892,7 @@ The low-level framework
 
 Behind the scenes, the high-level RSS framework uses a lower-level framework
 for generating feeds' XML. This framework lives in a single module:
-`django/utils/feedgenerator.py`_.
+:source:`django/utils/feedgenerator.py`.
 
 You use this framework on your own, for lower-level feed generation. You can
 also create custom feed generator subclasses for use with the ``feed_type``
@@ -1006,8 +1006,6 @@ For example, to create an Atom 1.0 feed and print it to standard output::
     ...
     </feed>
 
-.. _django/utils/feedgenerator.py: https://github.com/django/django/blob/master/django/utils/feedgenerator.py
-
 .. currentmodule:: django.contrib.syndication
 
 Custom feed generators