From 80da07e4b93bfbaf4dbadfd72fb58aa233fa0096 Mon Sep 17 00:00:00 2001
From: Malcolm Tredinnick <malcolm.tredinnick@gmail.com>
Date: Tue, 9 Dec 2008 07:32:28 +0000
Subject: [PATCH] The "permanent" parameter to redirect_to (r9594) is new in
 Django 1.1. Noted as much in the docs.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9625 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/ref/generic-views.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/ref/generic-views.txt b/docs/ref/generic-views.txt
index efa49e3ee3781..0c14c72cc3d29 100644
--- a/docs/ref/generic-views.txt
+++ b/docs/ref/generic-views.txt
@@ -136,6 +136,9 @@ If the given URL is ``None``, Django will return an ``HttpResponseGone`` (410).
       redirect will use status code 301. If ``False``, then the redirect will
       use status code 302. By default, ``permanent`` is ``True``.
 
+.. versionadded:: 1.1
+    The ``permanent`` keyword argument is new in Django 1.1.
+
 **Example:**
 
 This example issues a permanent redirect (HTTP status code 301) from