Say that ref/unref are thread-safe now. (#322883, Christophe Fergeau)

2006-04-18  Matthias Clasen  <mclasen@redhat.com>

	* gobject/tut_gobject.xml: Say that ref/unref are thread-safe now.
	(#322883, Christophe Fergeau)

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 6f74acb..e825507 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,8 @@
+2006-04-18  Matthias Clasen  <mclasen@redhat.com>
+
+       * gobject/tut_gobject.xml: Say that ref/unref are thread-safe now.  
+       (#322883, Christophe Fergeau)
+       
 2006-04-05  Matthias Clasen  <mclasen@redhat.com>
 
        * gobject/tmpl/signals.sgml: Document class_offset 0.

diff --git a/docs/reference/gobject/tut_gobject.xml b/docs/reference/gobject/tut_gobject.xml
index e790251..d928595 100644 (file)
--- a/docs/reference/gobject/tut_gobject.xml
+++ b/docs/reference/gobject/tut_gobject.xml
@@ -323,7 +323,7 @@ void        g_object_run_dispose          (GObject        *object);
 
        <para>
          The functions <function><link linkend="g-object-ref">g_object_ref</link></function>/<function><link linkend="g-object-unref">g_object_unref</link></function> respectively 
-         increase and decrease the reference count. None of these function is thread-safe.
+         increase and decrease the reference count.These functions are thread-safe as of GLib 2.8.
          The reference count is, unsurprisingly, initialized to one by 
          <function><link linkend="g-object-new">g_object_new</link></function> which means that the caller
           is currenly the sole owner of the newly-created reference.