| === xperia64_ is now known as xperia64 | ||
| Matombo444 | Hi, I'm wondering how the create new flavor, or create new fork process works for the ubuntu kernel repo | 17:18 |
|---|---|---|
| Matombo444 | 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:18 |
| Matombo444 | but i'm wondering also how the hwe fork is create from the non hwe one | 17:19 |
| Matombo444 | the non hwe one has all the configs and build stuff in debian.master | 17:19 |
| Matombo444 | the hwe one has all in debian.hwe-x.xx while debian.master still exists in that fork, but is unused? | 17:20 |
| Matombo444 | 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:20 |
| Matombo444 | So my question: Is the process of copying and altering debian.master to debian.hwe-x.xx automated with a script? | 17:22 |
| Matombo444 | And is the rebase to hold hwe in sync with non-hwe also somehow automatied with a script? | 17:23 |
| Matombo444 | 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 | 17:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!