Attachment #42042
[1/7] dbus_bus_set_unique_name, dbus_bus_get_unique_name: remember to unlock on OOM patch 2011-01-14 09:55:38 UTC 1.67 KB no flags Details
Attachment #42043
[2/2] bus-test: add support for only running one test patch 2011-01-14 09:56:14 UTC 4.66 KB no flags Details
Attachment #42044
[2/7 update_desktop_file_entry: use _dbus_strdup for something we'll dbus_free patch 2011-01-14 10:01:12 UTC 877 bytes no flags Details
Attachment #42045
update_desktop_file_entry: free exec_tmp in the successful case patch 2011-01-14 10:01:40 UTC 688 bytes no flags Details
Attachment #42046
[1/2] bus/test: assert that the client isn't listed, when appropriate patch 2011-01-14 10:03:05 UTC 1.36 KB no flags Details
Attachment #42168
[3/7] update_desktop_file_entry: make scope of exec_tmp as short as possible patch 2011-01-18 08:55:47 UTC 1.58 KB no flags Details
Attachment #42169
[4/7] update_desktop_file_entry: free @exec on error patch 2011-01-18 08:56:34 UTC 729 bytes no flags Details
Attachment #42170
[5/7] update_desktop_file_entry: don't double-free strings if added to entry before failure patch 2011-01-18 08:56:54 UTC 1.49 KB no flags Details
Attachment #42171
[6/7] update_desktop_file_entry: unify cleanup code for success and failure cases patch 2011-01-18 08:57:25 UTC 4.79 KB no flags Details
Attachment #42172
[7/7] _dbus_transport_get_is_authenticated: don't leak if copying GUID fails patch 2011-01-18 08:58:50 UTC 1.10 KB no flags Details
Attachment #42807
[7/7 v2] _dbus_transport_get_is_authenticated: don't leak if copying GUID fails patch 2011-02-01 05:29:20 UTC 1.36 KB no flags Details
Attachment #42808
[7/7 alternative] DBusTransport: don't copy DBusAuth's GUID to expected_guid patch 2011-02-01 05:31:02 UTC 2.13 KB no flags Details
Attachment #42809
update_desktop_file_entry: stylistic fixes based on Colin's review patch 2011-02-01 05:36:33 UTC 4.92 KB no flags Details

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.