You are not logged in.
Pages: 1
Alongside installing the Arch stable kernel and LTS kernel, I also build vanilla upstream regularly at certain times.
I'm mostly building until upstream Stable hits EOL (e.g. I'll be on 6.4.1[456]), while Arch is on a fresh new next Stable (6.5.[123]).
Previously, the Arch kernel maintenance for patches on top of upstream were committed in git. For instance, I'm still carrying this patch in my builds:
https://github.com/archlinux/linux/comm … f2bf02f6c0
Arch is still carrying that patch too, and the relevant flyspray for this issue was closed as completed when they started carrying the patch.
Looks like they've switched to having one big patchset. For instance, with 6.5.7:
https://github.com/archlinux/linux/rele … .patch.zst
...which still includes the aforementioned patch, jumbled in with everything else they're applying.
My questions:
1) Am I missing some easy way to see/find a list of individual patches Arch is maintaining on top of vanilla kernel?
2) Is any information or documentation available providing the rationale for applying the patches on the Arch kernel?
3) Is there a way to easily know when patches have been dropped for whatever reason (included upstream, obsoleted, superseded, etc.)?
Sure I can just look at the big patch mashup and discern changes, or can download both it and it's predecessor and diff them.
I'm hoping there's an easier way. Thanks @loqs ahead of time if you're the first to chime in here ![]()
Last edited by tekstryder (2023-10-19 13:33:19)
Offline
1) Am I missing some easy way to see/find a list of individual patches Arch is maintaining on top of vanilla kernel?
If you read the commit log for the v6.5.7-arch1 release you can see the applied patches: https://github.com/archlinux/linux/commits/v6.5.7-arch1
Last edited by progandy (2023-10-19 13:56:54)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
If you read the commit log...
Oh my, how embarrassing. I should have spent more time waking up and less time posting!
Was looking at main, not tags. Derp.
Last edited by tekstryder (2023-10-19 14:09:50)
Offline
See also https://bbs.archlinux.org/viewtopic.php?id=289067. You could ask for the patch to be generated by format-patch so it contains the metadata for each patch.
Offline
See also https://bbs.archlinux.org/viewtopic.php?id=289067. You could ask for the patch to be generated by format-patch so it contains the metadata for each patch.
Thanks for that. I had not seen that flyspray discussion on the decision, which seems a logical change in process.
Happily I'm not the only one that missed the obvious tags commit history haha.
Offline
Pages: 1