Repository navigation
History rewrite; commits 6ff5aa24a946, 6c0c4691e5bb lost #62
Description
It looks like your main branch got a forced push, losing two commits. This seems to be only a cosmetic measure. However, it affects other projects that link to these commits, e.g. in Git submodules. It would be nice if you could push these commits again, on a different branch or with a tag. This way you wouldn't have to keep them on the main branch, but they could still be checked out.
Activity
JonathonHall-Purism commentedon Aug 10, 2022
This breaks builds of coreboot releases that were referencing these commits (including 4.17, the most recent release). Coreboot has a mirror of this repo, but I believe it is an automated copy as the mirror also lost the commits.The commits have been restored on Coreboot's mirror, so Coreboot builds are working again.
intel-microcode: update SRCREV for 20220510
intel-microcode: update SRCREV for 20220510
intel-microcode: update SRCREV for 20220510
intel-microcode: update SRCREV for 20220510