**** BEGIN LOGGING AT Thu Dec 24 02:59:59 2015
Dec 24 04:18:12 <builder> build #182 of ramips.rt3883 is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/182
Dec 24 06:24:35 <builder> build #180 of imx6 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/180
Dec 24 07:28:16 <nitroshift> nbd, ping
Dec 24 07:30:51 <builder> build #184 of oxnas is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/oxnas/builds/184
Dec 24 10:20:51 <builder> build #184 of ramips.mt7628 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7628/builds/184
Dec 24 11:18:37 <builder> build #188 of ramips is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/188
Dec 24 11:44:08 <builder> build #183 of cobalt is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/183
Dec 24 11:47:01 <builder> build #183 of cns21xx is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/183
Dec 24 11:49:54 <builder> build #183 of orion is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/183
Dec 24 12:09:03 <builder> build #173 of rb532 is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/173
Dec 24 12:39:53 <builder> build #180 of pxa is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/180
Dec 24 14:00:56 <builder> build #147 of ixp4xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/147
Dec 24 15:46:10 <txomon> Hey, what is the difference between ubus_notify and ubus_send_event ?? I thought ubus_notify created events, but doesn't seem to be like that...
Dec 24 15:48:04 <txomon> if ubus_send_event is sending what you would call signals in dbus, what is ubus_notify's use case?
Dec 24 16:03:12 <nbd> events are global, notify is tied to an object
Dec 24 16:03:40 <nbd> also, notify allows you to check if somebody is listening
Dec 24 16:03:48 <nbd> to avoid generating messages when you don't have to
Dec 24 16:04:02 <nbd> you should use notify where possible
Dec 24 16:04:28 <nbd> also, notify allows you to gather responses from subscribers
Dec 24 16:35:37 <txomon> nbd: so it's more """reactive""" using notify than using calls all the time... ok
Dec 24 16:36:02 <txomon> but there is no ubus cli cmd for notifications, is there?
Dec 24 17:11:19 <nbd> right
Dec 24 18:43:18 <builder> build #149 of kirkwood is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/149
Dec 24 18:46:38 <builder> build #175 of ppc40x is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/175
Dec 25 02:42:56 <builder> build #183 of ramips.rt3883 is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/183
**** ENDING LOGGING AT Fri Dec 25 02:59:58 2015