[12:07] <jtaylor> hi, the lts-wily git is in a different location than the 3.x lts, will that stay like this?
[12:09] <jtaylor> the btrfs read corruption fixes that went into 3.x recently don't seem to be in 4.2 but I also don't know where the review branch is :/
[13:39] <apw> jtaylor, in a different place?  how so ?
[14:30] <jtaylor> apw: there are only 3.19 branches at kernel.ubuntu.com
[14:30] <jtaylor> while 4.2 seems to be on launchpad
[14:31] <apw> jtaylor, could you give me the URLs you are referring to
[14:32] <apw> jtaylor, as my ubuntu-trusty tree seems to have lts-backport-iwly in it
[14:32] <jtaylor> apw: kernel.ubuntu.com/ubuntu/linux.git
[14:32] <apw> jtaylor, that is just the stable trees, and 4.2 isn't under stable maintenance by us as yet i don't believe
[14:33] <apw> jtaylor, so that would be in gregkh's trees and he produced only the quilt forms
[14:33] <apw> jtaylor, but either way they don't represent the ubuntu kernel source
[14:34] <jtaylor> apw: what is the right one then?
[14:34] <jtaylor> I think I got that from the ubuntu docs
[14:34] <jtaylor> but that might have been a long time ago
[14:34] <apw> jtaylor, if you are looking for the source for linux-lts-wily in trusty that is on the lts-backport-wily branch in the ubuntu-trusty tree
[14:42] <jtaylor> apw: thx, what is the relation of that tree to the stable tree? will patches from the stable go into the lts backports?
[14:43] <jtaylor> seems lts-vivid is lagging ~3 month behind stable 3.19
[14:43] <apw> jtaylor, generally the answer to that is yes, we follow and apply the vast majority of the stable updates to the trees
[14:45] <apw> jtaylor, really?  vivid seems to have -ckt8 applied and -ckt9 is the latest
[14:46] <apw> which would make it a couple of weeks behind, which with us being at the start of a 3 week cycle, would be unsupprising
[14:46] <jtaylor> apw: I just looked at the btfs tree, last update there was in july
[14:46] <jtaylor> there have been a bunch of important fixes in stable since then
[14:46] <apw> jtaylor, do you have an example of a missing commit
[14:47] <jtaylor> though maybe they only got merged in recently so its probably ok
[14:49] <apw> jtaylor, if they are in -ctk9 then they will be in the next kernel upload
[14:49] <jtaylor> apw: 3276852 e.g. is from aug, but thats probably the author date not when it actually went into stable
[14:50] <jtaylor> so its probably fine
[14:50] <jtaylor> now I know where to look so I'll be patient, thanks
[14:52] <apw> jtaylor, right that appears in -ckt8, and vivid is -ckt7 in the last cycle, so we can expect that to be applied any day now for the next cycle