Member
See each individual change for the linked issues for more context.
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Member Author
2e1e313 is new in the latest push, as that failure happened overnight.
Contributor
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, LGTM.
I wonder though, if instead of providing the raw patches we could just have lore links that our system could fetch and apply? But as I'm writing this I realize that just complicates things. Food for thought, though.
Member Author
I've thought about that as well and came to the same conclusion. It may be nice to eventually have a step that tries to apply the patches first and remove any that fail to apply so that the build does not fail when patches fail to apply like it current does. However, the current scheme makes cleaning up the patches more obvious; if there is no clear signal that a patch no longer applies, we may not clean up the patches in between adding new ones.
Contributor
Merging ASAP since we have +2 review and we could potentially avoid some red in the matrix.
