Removed versionadded/changed annotations for 1.9.

docs/howto/auth-remote-user.txt

@@ -113,8 +113,6 @@ override one or more of its attributes and methods.
 Using ``REMOTE_USER`` on login pages only
 =========================================
 
-.. versionadded:: 1.9
-
 The ``RemoteUserMiddleware`` authentication middleware assumes that the HTTP
 request header ``REMOTE_USER`` is present with all authenticated requests. That
 might be expected and practical when Basic HTTP Auth with ``htpasswd`` or other

docs/howto/custom-file-storage.txt

@@ -94,11 +94,6 @@ the server or, if ``upload_to`` is a callable, the filename returned by that
 method after any path information is removed. Override this to customize how
 non-standard characters are converted to safe filenames.
 
-.. versionchanged:: 1.9
-
-    In older versions, this method was not called when ``upload_to`` was a
-    callable.
-
 The code provided on ``Storage`` retains only alpha-numeric characters, periods
 and underscores from the original filename, removing everything else.
 

docs/howto/custom-template-tags.txt

@@ -69,8 +69,6 @@ following::
 
     register = template.Library()
 
-.. versionadded:: 1.9
-
 Alternatively, template tag modules can be registered through the
 ``'libraries'`` argument to
 :class:`~django.template.backends.django.DjangoTemplates`. This is useful if
@@ -445,11 +443,6 @@ code does not contain XSS vulnerabilities. For building small HTML snippets,
 use of :func:`~django.utils.html.format_html` instead of ``mark_safe()`` is
 strongly recommended.
 
-.. versionchanged:: 1.9
-
-   Auto-escaping for ``simple_tag`` as described in the previous two paragraphs
-   was added.
-
 If your template tag needs to access the current context, you can use the
 ``takes_context`` argument when registering your tag::
 
@@ -490,8 +483,6 @@ positional arguments. For example:
 
     {% my_tag 123 "abcd" book.title warning=message|lower profile=user.profile %}
 
-.. versionadded:: 1.9
-
 It's possible to store the tag results in a template variable rather than
 directly outputting it. This is done by using the ``as`` argument followed by
 the variable name. Doing so enables you to output the content yourself where

docs/howto/error-reporting.txt

@@ -67,11 +67,6 @@ those are usually just people typing in broken URLs or broken Web bots. It also
 ignores 404s when the referer is equal to the requested URL, since this
 behavior is from broken Web bots too.
 
-.. versionchanged:: 1.9
-
-    In older versions, 404s were not ignored when the referer was equal to the
-    requested URL.
-
 .. note::
 
     :class:`~django.middleware.common.BrokenLinkEmailsMiddleware` must appear