The 18-arm64 branch is the basis for the new merged core/classic gadget. That is to say, that the other branches (18-armhf and classic) are to be trivial modifications from this branch. Hence, this PR should be reviewed first.
I did consider making the new classic branch the "base" and deriving from there, but for the time being it's easier to derive from core as it mostly involves removing stuff (like psplash) rather than derive from classic which would entail adding stuff (like psplash).
This PR appears complex but the way to view it is as a merge of 18-armhf into 18-arm64 (which was the first step, in the second-to-last commit after which the branches were identical), followed by modifications to make the branch "universal" (the last commit), so if you're happy with everything in the 18-armhf branch everything up to the second-to-last commit should be fine and it's only the last commit that requires review.
The 18-arm64 branch is the basis for the new merged core/classic gadget. That is to say, that the other branches (18-armhf and classic) are to be trivial modifications from this branch. Hence, this PR should be reviewed first.
I did consider making the new classic branch the "base" and deriving from there, but for the time being it's easier to derive from core as it mostly involves removing stuff (like psplash) rather than derive from classic which would entail adding stuff (like psplash).
This PR appears complex but the way to view it is as a merge of 18-armhf into 18-arm64 (which was the first step, in the second-to-last commit after which the branches were identical), followed by modifications to make the branch "universal" (the last commit), so if you're happy with everything in the 18-armhf branch everything up to the second-to-last commit should be fine and it's only the last commit that requires review.