Back to bug 33126

Who When What Removed Added
smcv 2011-01-14 10:00:32 UTC Keywords patch
Whiteboard patches are necessary but not sufficient
smcv 2011-01-18 08:55:47 UTC Attachment #42045 Attachment is obsolete 0 1
smcv 2011-01-18 08:59:26 UTC Attachment #42042 Attachment description dbus_bus_set_unique_name, dbus_bus_get_unique_name: remember to unlock on OOM [1/7] dbus_bus_set_unique_name, dbus_bus_get_unique_name: remember to unlock on OOM
smcv 2011-01-18 08:59:33 UTC Attachment #42044 Attachment description update_desktop_file_entry: use _dbus_strdup for something we'll dbus_free [2/7 update_desktop_file_entry: use _dbus_strdup for something we'll dbus_free
smcv 2011-01-18 08:59:49 UTC Attachment #42043 Attachment description bus-test: add support for only running one test [2/2] bus-test: add support for only running one test
smcv 2011-01-18 09:01:07 UTC Attachment #42046 Attachment description bus/test: assert that the client isn't listed, when appropriate [1/2] bus/test: assert that the client isn't listed, when appropriate
smcv 2011-01-18 09:01:45 UTC URL http://git.collabora.co.uk/?p=user/smcv/dbus-smcv.git;a=shortlog;h=refs/heads/leak-fixes
Whiteboard patches are necessary but not sufficient
smcv 2011-01-21 07:24:27 UTC Blocks 33337
smcv 2011-01-24 08:23:24 UTC Whiteboard 1.4
smcv 2011-01-26 09:31:36 UTC URL http://git.collabora.co.uk/?p=user/smcv/dbus-smcv.git;a=shortlog;h=refs/heads/leak-fixes http://git.collabora.co.uk/?p=user/smcv/dbus-smcv.git;a=shortlog;h=refs/heads/leak-fixes-33126
smcv 2011-01-27 09:05:30 UTC CC cosimo.alfarano, simon.mcvittie, thiago, walters
smcv 2011-02-01 04:20:18 UTC Attachment #42042 Attachment is obsolete 0 1
smcv 2011-02-01 04:20:39 UTC Attachment #42043 Attachment is obsolete 0 1
smcv 2011-02-01 05:29:20 UTC Attachment #42172 Attachment is obsolete 0 1
smcv 2011-02-17 09:23:12 UTC Status ASSIGNED RESOLVED
Resolution --- FIXED

Back to bug 33126

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.