[00:13]  * RAOF unplugs his external monitor, causing all Qt apps to crash (as usual).
[00:15] <greyback> I really hate that
[00:16] <greyback> fixed in qt5.5!
[00:17] <RAOF> YAY!
[00:18] <RAOF> We should go back and close those Qt bugs, then :)
[00:32] <racarr> RAOF: s'ok im hooked on kindle now
[00:33] <RAOF> Fair enough.
[00:33] <RAOF> The physical copy is pretty nice, though ;)
[00:33] <RAOF> Also, you should read it :)
[00:33] <racarr> well ok if you remember :D
[00:33] <racarr> yeah I will...I've been stuck on this one book for like
[00:33] <racarr> almost 2 months now I guess whoops
[00:34] <racarr> I think I may just give up trying to extract meaning from this long rambling middle section and
[00:34] <racarr> power through lol
[00:34] <racarr> "2666"
[00:34] <racarr> ouch jenkins had a murder run on me
[00:34] <racarr> conflicts I bet
[00:42] <RAOF> :)
[00:51] <RAOF> Hm. It's trying quite hard to sleet here.
[00:52] <racarr> eww
[00:53] <RAOF> It's failing, and just dropping very cold rain, but it's trying.
[01:04] <racarr> ah phones were having network issues
[01:04] <racarr> and I had a memory error
[01:12] <RAOF> Always the best!
[01:20] <racarr> there have been a few funny test failures
[01:20] <racarr> in this event cleaning pipeline where its
[01:21] <racarr> basically tests were relying on behavior that converted an invalid android event
[01:21] <racarr> to an invalid mir event
[01:21] <racarr> so
[01:21] <racarr> so
[01:21] <racarr> many
[01:21] <racarr> invalid states
[01:46] <duflu> racarr: Isn't that better than an invalid Android event yielding a valid Mir event? :)
[02:09] <RAOF> Oops. Filesystem corruption after hard power-off.
[03:06] <RAOF> You know, this code that I'm writing right now could really do with Rust's borrow checker.
[03:07] <RAOF> None of these shared_ptrs are *actually* shared. I'm using guarantees about their lifetimes that are manually maintained.
[06:47] <duflu> Funny thing happens when you achieve low render latency - the LCD persistence (motion blur) becomes more noticeable
[08:34] <alan_g> alf_: you agree I can TA this? https://code.launchpad.net/~unity-system-compositor-team/unity-system-compositor/trunk/+merge/258047
[08:35] <alf_> alan_g: approval still stands
[08:46] <alan_g> Is there an easy way to find the "image number" of a phone install?
[09:12] <duflu> alan_g: system-image-cli -i    ?
[09:13] <alan_g> duflu: thanks
[16:51] <racarr> alf_: With the pointer buttons I do mean running out of bits ... do you have another idea?
[16:51] <racarr> It may be ok to say 64 bits and call it done...
[16:52] <racarr> I guess what im worried about is some devices will have buttons that I guess dont correspond
[16:52] <racarr> to MirPointerButton and can only be interpreted through the device introspection API (perhaps this is true? Maybe it's not really...)
[16:52] <racarr> and that could get weird if things were flags
[19:41] <racarr> Does anyone have a good writeup of what is going on in situations where bzr merge --weave will fix conflicts that merge wont
[19:41] <racarr> ive never bothered to understand it and it always leaves me with this
[19:41] <racarr> sinking uneasy feeling
[19:45] <racarr> man there could be a way better interface for managing
[19:45] <racarr> pipelined branches...
[19:45] <racarr> e.g. if launchpad
[19:45] <racarr> understood it
[19:46] <racarr> also I have to put a dollar in the gender specific noun when addressing a general audience jar :(