There are 1,645 commits between torvalds/linux@v6.11 and edera-dev/linux-openpax@v6.11.x-openpax.
For package maintainers who would like to apply OpenPaX patches it would be very helpful if a roll-up patch-set could be released/tagged for each upstream release and point-update, or if this repo could be tagged/branched in such a way as to allow a minimal set of changes to be identified against upstream:
In order to control the space consumed by kernel-sources, the current process is that the upstream release (e.g. v6.11) is downloaded once, and then for each new point-release a separate incremental patch is applied over the (previously-patched point) release.
Being able to apply a trivially-generated v6.11.2-openpax diff onto a v6.11+v6.11.1+v6.11.2 source-tree (where v6.11.2 may be behind the HEAD of the v6.11.x-openpax branch) would be ideal!
There are 1,645 commits between torvalds/linux@v6.11 and edera-dev/linux-openpax@v6.11.x-openpax.
For package maintainers who would like to apply OpenPaX patches it would be very helpful if a roll-up patch-set could be released/tagged for each upstream release and point-update, or if this repo could be tagged/branched in such a way as to allow a minimal set of changes to be identified against upstream:
In order to control the space consumed by kernel-sources, the current process is that the upstream release (e.g.
v6.11) is downloaded once, and then for each new point-release a separate incremental patch is applied over the (previously-patched point) release.Being able to apply a trivially-generated
v6.11.2-openpaxdiff onto av6.11+v6.11.1+v6.11.2source-tree (wherev6.11.2may be behind the HEAD of thev6.11.x-openpaxbranch) would be ideal!