| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| tjaalton | bregma: ping? did you see my question from yesterday? | 05:08 |
|---|---|---|
| duflu | tjaalton: I suspect it's around 1am for him | 05:10 |
| duflu | or 12am | 05:10 |
| duflu | which confusingly comes before 1am | 05:11 |
| tjaalton | oh | 05:13 |
| duflu | Unusual problem... all my branches' tests all pass on an Android device. So what's up with CI? | 05:34 |
| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| duflu | Won some, lost some. | 10:08 |
| duflu | Good night | 10:08 |
| 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:57 |
| * 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 | 10:58 |
| 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:10 |
| greyback | alan_g: yep, that can go. I don't see anything useful in it anyway | 12:12 |
| greyback | it was originally used just to know when Mir had started | 12:13 |
| alan_g | greyback: ah, now obsolete for that purpose. :) | 12:14 |
| greyback | yep | 12:14 |
| === chihchun is now known as chihchun_afk | ||
| === hikiko_ is now known as hikiko|ln | ||
| === chihchun_afk is now known as chihchun | ||
| === hikiko|ln is now known as hikiko | ||
| === kdub_ is now known as kdub | ||
| === mcs__ is now known as mcs_ | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!