From 1cf14de82f3ad4beceeeb9ba555763ef8d70ed24 Mon Sep 17 00:00:00 2001
From: Ryan Lortie <desrt@desrt.ca>
Date: Tue, 2 Nov 2010 22:12:55 -0400
Subject: [PATCH] docs: Recommend against using GTimeVal

---
 docs/reference/glib/tmpl/date.sgml | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/docs/reference/glib/tmpl/date.sgml b/docs/reference/glib/tmpl/date.sgml
index 54b38cb..ca82020 100644
--- a/docs/reference/glib/tmpl/date.sgml
+++ b/docs/reference/glib/tmpl/date.sgml
@@ -52,10 +52,7 @@ representation is valid. Sometimes neither is valid. Use the API.
 </para>
 
 <para>
-GLib doesn't contain any time-manipulation functions; however, there
-is a #GTime typedef and a #GTimeVal struct which represents a more 
-precise time (with microseconds). You can request the current time as 
-a #GTimeVal with g_get_current_time().
+GLib also features #GDateTime which represents a precise time.
 </para>
 
 <!-- ##### SECTION See_Also ##### -->
@@ -84,6 +81,12 @@ Similar to the <structname>struct timeval</structname> returned by
 the <function>gettimeofday()</function> UNIX call.
 </para>
 
+<para>
+GLib is attempting to unify around the use of 64bit integers to
+represent microsecond-precision time.  As such, this type will be
+removed from a future version of GLib.
+</para>
+
 @tv_sec: seconds
 @tv_usec: microseconds
 
-- 
2.7.4