textchan-group: improve debug |
patch
|
2014-03-10 20:40:06 UTC |
1.64 KB |
no flags
|
Details |
Use concrete dbus-glib parameterized types, not G_TYPE_VALUE_ARRAY |
patch
|
2014-03-10 20:40:25 UTC |
2.30 KB |
no flags
|
Details |
TpContact: mime_file_written: don't leak the file's path |
patch
|
2014-03-10 20:41:06 UTC |
1.34 KB |
no flags
|
Details |
TpTestsContactsConnection: don't leak list_manager |
patch
|
2014-03-10 20:41:19 UTC |
1.24 KB |
no flags
|
Details |
Ignore allocations in gobject_init_ctor |
patch
|
2014-03-10 20:41:31 UTC |
646 bytes |
no flags
|
Details |
TpBaseContactList: don't leak groups hash table |
patch
|
2014-03-10 20:42:04 UTC |
790 bytes |
no flags
|
Details |
TpProxy: finish_all_requests: don't leak copied GQueue |
patch
|
2014-03-10 20:42:17 UTC |
668 bytes |
no flags
|
Details |
account test: don't leak copied strings |
patch
|
2014-03-10 20:42:28 UTC |
1.32 KB |
no flags
|
Details |
TpTestsSimpleChannelDispatcher: don't leak various struct members |
patch
|
2014-03-10 20:42:41 UTC |
2.10 KB |
no flags
|
Details |
cli-group test: don't leak GMainLoop |
patch
|
2014-03-10 20:42:52 UTC |
692 bytes |
no flags
|
Details |
channel-introspect test: enable debug-logging |
patch
|
2014-03-10 20:43:04 UTC |
773 bytes |
no flags
|
Details |
tests: extend timeout |
patch
|
2014-03-10 20:43:20 UTC |
730 bytes |
no flags
|
Details |
GDBus can deliver more than one event per main-loop iteration |
patch
|
2014-03-10 20:44:13 UTC |
6.44 KB |
no flags
|
Details |
dbus test: don't re-enter main loop to request/release names |
patch
|
2014-03-10 20:45:35 UTC |
3.83 KB |
no flags
|
Details |
invalidated-while-invoking-signals test: move to GTest |
patch
|
2014-03-10 20:45:47 UTC |
4.24 KB |
no flags
|
Details |
invalidated-while-invoking-signals test: extend test coverage |
patch
|
2014-03-10 20:46:01 UTC |
4.24 KB |
no flags
|
Details |
tp_tests_assert_last_unref: add |
patch
|
2014-03-10 20:46:37 UTC |
1.60 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.