Removed references to changes made in 1.2.

Thanks Florian Apolloner for the patch.

3 files changed, 0 insertions, 25 deletions

diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 629efc0432..23dcf4bd9f 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -208,8 +208,6 @@ automatically generated from the model class. Default is ``True``.
 ``error_messages``
 ------------------
 
-.. versionadded:: 1.2
-
 .. attribute:: Field.error_messages
 
 The ``error_messages`` argument lets you override the default messages that the
@@ -309,8 +307,6 @@ underscores to spaces. See :ref:`Verbose field names <verbose-field-names>`.
 ``validators``
 -------------------
 
-.. versionadded:: 1.2
-
 .. attribute:: Field.validators
 
 A list of validators to run for this field. See the :doc:`validators
@@ -336,8 +332,6 @@ otherwise. See :ref:`automatic-primary-key-fields`.
 ``BigIntegerField``
 -------------------
 
-.. versionadded:: 1.2
-
 .. class:: BigIntegerField([**options])
 
 A 64 bit integer, much like an :class:`IntegerField` except that it is
@@ -357,11 +351,6 @@ The admin represents this as a checkbox.
 If you need to accept :attr:`~Field.null` values then use
 :class:`NullBooleanField` instead.
 
-.. versionchanged:: 1.2
-    In previous versions of Django when running under MySQL ``BooleanFields``
-    would return their data as ``ints``, instead of true ``bools``.  See the
-    release notes for a complete description of the change.
-
 ``CharField``
 -------------
 
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
index 50fb085d38..3ae994bc5b 100644
--- a/docs/ref/models/instances.txt
+++ b/docs/ref/models/instances.txt
@@ -30,8 +30,6 @@ that, you need to :meth:`~Model.save()`.
 Validating objects
 ==================
 
-.. versionadded:: 1.2
-
 There are three steps involved in validating a model:
 
 1. Validate the model fields
@@ -137,9 +135,6 @@ To save an object back to the database, call ``save()``:
 
 .. method:: Model.save([force_insert=False, force_update=False, using=DEFAULT_DB_ALIAS, update_fields=None])
 
-.. versionadded:: 1.2
-   The ``using`` argument was added.
-
 If you want customized saving behavior, you can override this ``save()``
 method. See :ref:`overriding-model-methods` for more details.
 
@@ -361,9 +356,6 @@ Deleting objects
 
 .. method:: Model.delete([using=DEFAULT_DB_ALIAS])
 
-.. versionadded:: 1.2
-   The ``using`` argument was added.
-
 Issues a SQL ``DELETE`` for the object. This only deletes the object in the
 database; the Python instance will still exist and will still have data in
 its fields.
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 050598a532..eef22728ab 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -727,8 +727,6 @@ passed to ``select_related()``. This includes foreign keys that have
 It's an error to use both a list of fields and the ``depth`` parameter in the
 same ``select_related()`` call; they are conflicting options.
 
-.. versionchanged:: 1.2
-
 You can also refer to the reverse direction of a
 :class:`~django.db.models.OneToOneField` in the list of fields passed to
 ``select_related`` — that is, you can traverse a
@@ -1156,8 +1154,6 @@ using
 
 .. method:: using(alias)
 
-.. versionadded:: 1.2
-
 This method is for controlling which database the ``QuerySet`` will be
 evaluated against if you are using more than one database.  The only argument
 this method takes is the alias of a database, as defined in
@@ -1512,8 +1508,6 @@ exists
 
 .. method:: exists()
 
-.. versionadded:: 1.2
-
 Returns ``True`` if the :class:`.QuerySet` contains any results, and ``False``
 if not. This tries to perform the query in the simplest and fastest way
 possible, but it *does* execute nearly the same query. This means that calling