[01:52] <stefanct> hi. one of my patches was accepted upstream including the longterm kernels including the 4.4 branch. i have noticed that xenial's kernel follows the 4.4 stable branch but is some versions behind with security fixes applied only although it was updated more frequently up to 4.4.30
[01:53] <stefanct> since id like to use my patch without keeping my own kernel id like to know why this is the case and if it will follow upstream more closely again in the future
[02:47] <JanC> stefanct: did you file a bug report?
[03:16] <sbeattie> stefanct: if you look at the xenial kernel tree, master-next is up to 4.4.34 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/log/?h=master-next ; unfortunately, it didn't make it into the 4.4.0-49.70 that's currently in xenial-proposed, but unless there's a problem with the patch, it should make it in the next SRU cycle, ending roughly Dec 19th: https://lists.ubuntu.com/archives/kernel-sru-announce/2016-November/0
[03:16] <sbeattie> 00077.html
[03:16] <sbeattie> bah, silly client, last url should be https://lists.ubuntu.com/archives/kernel-sru-announce/2016-November/000077.html
[09:45] <stefanct> JanC: no, there is really no reason to create unnecessary work for anybody :) sbeattie: thanks! i was only looking at the changelog(s) and there not much was going on. i can easily work around it till then.
[17:59] <stgraber> bjf: assuming it's your bot having fun with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639345, why did it perform that last change (New -> Incomplete) AFTER I added the bot-stop-nagging tag?
[17:59] <ubot5`> Ubuntu bug 1639345 in linux (Ubuntu) "lxc-attach to malicious container allows access to host" [Undecided,Triaged]