[gtk+/composite-templates] Expand the thread deprecation documentation

[Juan Pablo Ugarte <jpu src gnome org>]

commit 7000f405a1d30e33d86961299abe4e43ae6f16cc
Author: Matthias Clasen <mclasen redhat com>
Date:   Wed Aug 1 10:26:17 2012 +0200

    Expand the thread deprecation documentation
    
    The story is slightly different for applications vs libraries;
    make it clear that libraries should continue using the lock so
    we don't break applications that haven't been ported to the
    'single thread' model yet.

 gdk/gdk.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/gdk/gdk.c b/gdk/gdk.c
index 752625e..6c354b1 100644
--- a/gdk/gdk.c
+++ b/gdk/gdk.c
@@ -661,7 +661,9 @@ gdk_init (int *argc, char ***argv)
  * it is recommended to use g_idle_add(), g_main_context_invoke()
  * and similar functions to make these calls from the main thread
  * instead. The main thread is the thread which has called gtk_init()
- * and is running the GTK+ mainloop.
+ * and is running the GTK+ mainloop. GTK+ itself will continue to
+ * use the GDK lock internally as long as the deprecated functionality
+ * is still available, and other libraries should probably do the same.
  */