From: Havoc Pennington <hp@redhat.com>
Date: Tue, 6 Jun 2006 20:28:57 +0000 (+0000)
Subject: the recursive locks todo item was a little misleading
X-Git-Tag: dbus-0.62~14
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cd766664ac832e75746ee59dd52915de39a20ac2;p=thirdparty%2Fdbus.git

the recursive locks todo item was a little misleading
---

diff --git a/doc/TODO b/doc/TODO
index 7108734c5..1f70e859d 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -4,10 +4,10 @@ Important for 1.0
  - add a new return code from dbus_connection_dispatch() called 
    IN_PROGRESS or RECURSED or something, indicating that DATA_REMAINS
    but another dispatch is in progress, so we can't dispatch at 
-   this time. Fixes the recursive deadlock. See the @todo for more
+   this time. OR maybe just switch to recursive locks for the dispatch 
+   locks. Fixes the recursive deadlock. See the @todo for more
    and this thread: http://lists.freedesktop.org/archives/dbus/2006-February/004128.html
 
-
  - Remove all deprecated functions
 
  - Audit @todo and FIXME for security issues