=== ogasawara is now known as Guest59904 [12:07] hi, the lts-wily git is in a different location than the 3.x lts, will that stay like this? [12:09] 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] jtaylor, in a different place? how so ? [14:30] apw: there are only 3.19 branches at kernel.ubuntu.com [14:30] while 4.2 seems to be on launchpad [14:31] jtaylor, could you give me the URLs you are referring to [14:32] jtaylor, as my ubuntu-trusty tree seems to have lts-backport-iwly in it [14:32] apw: kernel.ubuntu.com/ubuntu/linux.git [14:32] 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] jtaylor, so that would be in gregkh's trees and he produced only the quilt forms [14:33] jtaylor, but either way they don't represent the ubuntu kernel source [14:34] apw: what is the right one then? [14:34] I think I got that from the ubuntu docs [14:34] but that might have been a long time ago [14:34] 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 === Ursinha_ is now known as Ursinha [14:42] 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] seems lts-vivid is lagging ~3 month behind stable 3.19 [14:43] jtaylor, generally the answer to that is yes, we follow and apply the vast majority of the stable updates to the trees [14:45] jtaylor, really? vivid seems to have -ckt8 applied and -ckt9 is the latest [14:46] 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] apw: I just looked at the btfs tree, last update there was in july [14:46] there have been a bunch of important fixes in stable since then [14:46] jtaylor, do you have an example of a missing commit [14:47] though maybe they only got merged in recently so its probably ok [14:49] jtaylor, if they are in -ctk9 then they will be in the next kernel upload [14:49] apw: 3276852 e.g. is from aug, but thats probably the author date not when it actually went into stable [14:50] so its probably fine [14:50] now I know where to look so I'll be patient, thanks [14:52] 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 === luc4_ is now known as luc4