Bladeren bron

Updated some outdated external URLs in docs.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17710 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Claude Paroz 13 jaren geleden
bovenliggende
commit
21fb1c59c3

+ 2 - 2
docs/howto/static-files.txt

@@ -469,8 +469,8 @@ For details on how you'd write one of these backends,
     storage backends for many common file storage APIs (including `S3`__).
 
 __ http://s3.amazonaws.com/
-__ http://code.welldev.org/django-storages/
-__ http://code.welldev.org/django-storages/wiki/S3Storage
+__ http://code.larlet.fr/django-storages/
+__ http://django-storages.readthedocs.org/en/latest/backends/amazon-S3.html
 
 Upgrading from ``django-staticfiles``
 =====================================

+ 1 - 1
docs/internals/contributing/committing-code.txt

@@ -83,7 +83,7 @@ repository:
 
   For the curious: we're using a `Trac post-commit hook`_ for this.
 
-  .. _Trac post-commit hook: http://trac.edgewall.org/browser/trunk/contrib/trac-post-commit-hook
+  .. _Trac post-commit hook: http://trac.edgewall.org/browser/trunk/contrib/trac-svn-post-commit-hook.cmd
 
 * If your commit references a ticket in the Django `ticket tracker`_ but
   does *not* close the ticket, include the phrase "Refs #abc", where "abc"

+ 1 - 1
docs/internals/contributing/writing-code/submitting-patches.txt

@@ -160,7 +160,7 @@ binary, so relinking that command may be necessary as well.
 Please don't forget to run ``compress.py`` and include the ``diff`` of the
 minified scripts when submitting patches for Django's javascript.
 
-.. _Closure Compiler: http://code.google.com/closure/compiler/
+.. _Closure Compiler: https://developers.google.com/closure/compiler/
 .. _django-developers: http://groups.google.com/group/django-developers
 .. _list of tickets with patches: https://code.djangoproject.com/query?status=new&status=assigned&status=reopened&has_patch=1&order=priority
 .. _ticket tracker: https://code.djangoproject.com/newticket

+ 1 - 1
docs/ref/contrib/gis/db-api.txt

@@ -30,7 +30,7 @@ MySQL Spatial Limitations
 
 MySQL's spatial extensions only support bounding box operations
 (what MySQL calls minimum bounding rectangles, or MBR).  Specifically,
-`MySQL does not conform to the OGC standard <http://dev.mysql.com/doc/refman/5.1/en/functions-that-test-spatial-relationships-between-geometries.html>`_:
+`MySQL does not conform to the OGC standard <http://dev.mysql.com/doc/refman/5.1/en/functions-for-testing-spatial-relations-between-geometric-objects.html>`_:
 
     Currently, MySQL does not implement these functions
     [``Contains``, ``Crosses``, ``Disjoint``, ``Intersects``, ``Overlaps``,