=== xperia64_ is now known as xperia64 [17:18] Hi, I'm wondering how the create new flavor, or create new fork process works for the ubuntu kernel repo [17:18] with some help i found https://help.ubuntu.com/community/Kernel/Compile#Modify_the_source_for_your_needs which explains how to create a new flavor [17:19] but i'm wondering also how the hwe fork is create from the non hwe one [17:19] the non hwe one has all the configs and build stuff in debian.master [17:20] the hwe one has all in debian.hwe-x.xx while debian.master still exists in that fork, but is unused? [17:20] and looking at the git log of the hwe kernel there seems to be some kind of rebase every time a new version gets released [17:22] So my question: Is the process of copying and altering debian.master to debian.hwe-x.xx automated with a script? [17:23] And is the rebase to hold hwe in sync with non-hwe also somehow automatied with a script? [17:24] with non hwe i mean the original repo of the specific ubuntu version, e.g. non-hwe -> jammy kernel 5.15, hwe -> focal hwe kernel 5.15 which is based on the jammy 5.15 kernel