[08:19] <apw> backjlack, yes, that i am sure we have talked about before, and it is because upstream renamed that config section, and the debug kernel builder cannot know that they did so, so it is disabled
[08:19] <apw> those builds are not intended to be used for anything other than bug isolation, so they are dirty builds
[10:03]  * ogra_ lols seeing apw's typo in the last linux upload 
[10:05] <ogra_> (ubuntus kernel is now 100% probiotic thanks to dracult)
[10:59] <apw> ogra_, spelling is definatly not one of my strong suits
[11:00] <ogra_> but i love this one :)
[11:47] <amitk> ogra_: probiotic is what healthy yogurt is, isn't it? good thing....
[11:47] <ogra_> :)
[13:23] <cking> the latest kernel keeps you healthy and regular
[15:03] <jsalisbury> ##
[15:03] <jsalisbury> ## Kernel team meeting today @ 17:00 UTC
[15:03] <jsalisbury> ##
[15:04] <backjlack> apw: I've just reported that in case it wasn't known, nothing less, nothing more.
[15:09] <apw> backjlack, ack
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Meeting starting now
[17:00] <jsalisbury> ##
[19:15] <infinity> zequence: http://launchpad.net/bugs/1435582
[22:00] <rbasak> Terrible performance using IPv6 (IPv4 was fine) over a Precise kernel bridge running 3.2.0-77.114. Down to about 2 MB/s. I tried linux-image-generic-lts-trusty and it's fine (~90 MB/s as expected).
[22:00] <rbasak> I wonder why Precise's kernel was so bad, but for IPv6 only?