[05:08] <tjaalton> bregma: ping? did you see my question from yesterday?
[05:10] <duflu> tjaalton: I suspect it's around 1am for him
[05:10] <duflu> or 12am
[05:11] <duflu> which confusingly comes before 1am
[05:13] <tjaalton> oh
[05:34] <duflu> Unusual problem... all my branches' tests all pass on an Android device. So what's up with CI?
[10:08] <duflu> Won some, lost some.
[10:08] <duflu> Good night
[10:57] <alan_g> greyback: I assume the "miral integration" churn has died down and
[10:57] <alan_g> I can resume tidying qtmir?
[10:57] <greyback> alan_g: the foundation landed yes, I've child surface support to land yet
[10:58]  * alan_g is hoping that is orthogonal to the remaining libmirserver deps
[10:58] <alan_g> It *should* be.
[10:58] <greyback> alan_g: I think so, you should be free
[12:10] <alan_g> greyback: am I missing something? Is there a (current) purpose to MirServerStatusListener? It seems reasonable to want to detect these state transitions, but AFAICS they are ignored.
[12:12] <greyback> alan_g: yep, that can go. I don't see anything useful in it anyway
[12:13] <greyback> it was originally used just to know when Mir had started
[12:14] <alan_g> greyback: ah, now obsolete for that purpose. :)
[12:14] <greyback> yep