[10:23] <alan_g> alf_: anpok - any opinions pending on this? https://code.launchpad.net/~kdub/mir/report-vsync/+merge/251532
[10:31] <anpok> taking a look
[11:26] <duflu> alan_g: I'm still concerned about the accuracy. The report function is called some unbounded time after vsync. But in the case of constant rendering, it will usually be fairly close
[11:26] <duflu> We have the same trade-off in our perf reports already
[11:26] <duflu> And that's enough.
[16:41] <alan_g> On the BBC: http://m.bbc.co.uk/news/technology-31723029
[19:58] <ameurux> hello
[21:28] <kenvandine> i hear there a way to make mir logging more verbose, any pointers?
[21:36] <anpok> kenvandine: http://unity.ubuntu.com/mir/component_reports.html
[21:36] <kenvandine> anpok, thx
[21:53] <anpok> kenvandine: two are missing shared-library-prober-report and compositor-report (fixing that)
[21:59] <tmpRAOF> Hm. That reminds me. Should turn shared
[21:59] <tmpRAOF> Hm. That reminds me. Should turn shared-library-prober-report into some unconditional logging.
[22:06] <anpok> hm hm
[22:06] <anpok> but meanwhile it gets documented
[22:12] <tmpRAOF> Absolutely.