[09:49] <LocutusOfBorg> apw, please sync vbox kernel modules :p
[13:19] <jcastro> jsalisbury: if you're around can we talk about https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654 ? 
[13:20] <jsalisbury> jcastro, sure
[13:20] <jcastro> oh you're awake, I wasn't expecting that. :D
[13:20] <jsalisbury> heh, yeah.
[13:20] <jsalisbury> jcastro, that is an old bug
[13:21] <jcastro> hey so, the vivid and utopic tags
[13:21] <jcastro> if I wanted to make the case to bring this to $current_animal, how do I do that?
[13:21] <jsalisbury> jcastro, you can just add the xenail, yakkety and zesty tags.  
[13:22] <jsalisbury> jcastro, then probably just set the status to "New" instead of triaged or invalid
[13:22] <jsalisbury> jcastro, setting it new makes it pop back up on my radar
[13:23] <jcastro> do I leave the old release tags on there also?
[13:23] <jsalisbury> jcastro, sure, it doesnt hurt anything
[13:24] <jcastro> tags aren't the same as nominating for a series in lp are they? 
[13:25] <jsalisbury> jcastro, no, the tags are just used for reports, mail filter and things like that.  Nomimating them for a series is where you would want to set the status to "Invalid" for utopic and other EOL releases
[13:26] <jcastro> oh ok, we'll I messed that up, sorry, heh
[13:26] <jsalisbury> that bug doesn't seem to have any nominations yet, but I can add them
[13:26] <jsalisbury> jcastro, oh nevermind, you did already :-)
[13:27] <jsalisbury> jcastro, I'll take a closer look at that bug today and see what can be done to resolve it.
[13:28] <jcastro> hey so I wanted to convince the guy who was bugging me about it to send a patch
[13:28] <jsalisbury> jcastro, I also added the tag "kernel-da-key".  That makes sure I see and read all email/comments for the bug
[13:29] <jsalisbury> jcastro, yeah, if he already has a patch that would be great
[13:29] <jcastro> he won't use lp or bzr though, this seems like a packaging bug, is there a git workflow?
[13:31] <jsalisbury> jcastro, sure, he can use "git format-patch" and email it to the kernel-team mailing list
[13:31] <jcastro> excellente, I'll encourage him to do that
[13:31] <jsalisbury> jcastro, great
[13:32] <jcastro> I was blindsided by "hey you guys haven't fixed this bug in 3 years" and I was like dang, at least try to ask somebody
[13:32] <jsalisbury> jcastro, heh, yeah.  bugs usually expire after 6 months if there is no activity
[13:32] <jcastro> right
[13:33] <jcastro> also my "I thought mangled was the entire point of C++" probably didn't go over well lol. 
[13:33] <jsalisbury> haha
[13:33] <Vej> Hello! Could someone with knowledge about the kernel update process point Simon Davis (and me) to a resource about inclusion of that fix into the upstream stable. I run out of knowledge and manuals. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663991
[13:35] <jsalisbury> Vej, I'll add a comment
[13:35] <Vej> jsalisbury: Thank you very much!
[13:35] <jsalisbury> np
[13:43] <jcastro> jsalisbury: in hindsight, https://wiki.ubuntu.com/Kernel/Dev/KernelPatches is awesome
[13:43] <jcastro> I wish I would have found that first
[13:44] <Vej> jsalisbury: I am sorry, but that left more questions to me than clarifying things. That patch is already accepted into 4.10.1 (see https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=a810007afe239d59c1115fcaa06eb5b480f876e9). Do we need to submit it again to get it integrated into  4.4.X, or will you cherry-pick/include from 4.10.1?
[14:38] <jtaylor> is it possible to add some kind of automated test for bug 1396654? quite annoying having it break every few releases