From d3c75da7fbcdf5d32ab332c9de276e1ffd15f312 Mon Sep 17 00:00:00 2001
From: Kristian Glass <git@doismellburning.co.uk>
Date: Fri, 22 Aug 2014 12:24:46 +0200
Subject: [PATCH] [1.6.x] Fixed #23342 -- Clarified warning about naive time
 objects.

Thanks to apollo13 for suggested wording.

Backport of b7336ec179 from master
---
 docs/topics/i18n/timezones.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index 38d412df5a9..ae869f23575 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -102,7 +102,8 @@ should be aware too. In this mode, the example above becomes::
     lead to questionable usefulness".
 
     Django only supports naive time objects and will raise an exception if you
-    attempt to save an aware time object.
+    attempt to save an aware time object, as a timezone for a time with no
+    associated date does not make sense.
 
 .. _naive-datetime-objects: