On Tue, 2016-05-31 at 23:33 -0400, Nicholas D Steeves wrote: > On 24 May 2016 at 22:23, Ben Hutchings <ben@decadent.org.uk> wrote: > > On Tue, 2016-05-24 at 21:51 -0400, Nicholas D Steeves wrote: > > > Dear Debian Kernel Team, > > > > > > My primary area of interest is btrfs on Debian. The most reliable way > > > of limiting one's risk while using this experimental file system is to > > > run the most recent LTS kernel, and to minimize the use of exotic > > > features, or in some cases not use them at all (eg: RAID56 which > > > doesn't yet have proven scrub/self healing support). In the interest > > > of providing the most stable btrfs experience to users of Debian > > > stable, would it be possible to fork the jessie-backport of src:linux > > > from 4.4.6-1, update it to 4.4.11-1, and then continue to maintain the > > > branch? > > > > > > I believe I am underqualified to maintain it myself, but if it would > > > be sufficient to learn the workflow of patch-level updates to the > > > src:linux-derived package, then I might be able to help with the > > > effort. > > > > That's not how Debian backports suites work, sorry. > > Am I correct in understanding that it's also impossible to get > src:linux-4.4 and btrfs-progs-4.4 into jessie-updates? Correct. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer.
Attachment:
signature.asc
Description: This is a digitally signed message part