-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History rewrite; commits 6ff5aa24a946, 6c0c4691e5bb lost #62
Comments
The commits have been restored on Coreboot's mirror, so Coreboot builds are working again. |
doanac
pushed a commit
to lmp-mirrors/meta-intel
that referenced
this issue
Aug 11, 2022
The commit 6c0c4691e5bb446e0e428ebca595164709c59586 is missing in upstream https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files. Reference: intel/Intel-Linux-Processor-Microcode-Data-Files#62. Use 925555515555 instead of 6c0c4691e5bb. The difference between those two commits are just some "^M" fixes in releasenote.md. Signed-off-by: Yongxin Liu <[email protected]> Signed-off-by: Anuj Mittal <[email protected]>
doanac
pushed a commit
to lmp-mirrors/meta-intel
that referenced
this issue
Aug 11, 2022
The commit 6c0c4691e5bb446e0e428ebca595164709c59586 is missing in upstream https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files. Reference: intel/Intel-Linux-Processor-Microcode-Data-Files#62. Use 925555515555 instead of 6c0c4691e5bb. The difference between those two commits are just some "^M" fixes in releasenote.md. Signed-off-by: Yongxin Liu <[email protected]> Signed-off-by: Anuj Mittal <[email protected]>
doanac
pushed a commit
to lmp-mirrors/meta-intel
that referenced
this issue
Aug 11, 2022
The commit 6c0c4691e5bb446e0e428ebca595164709c59586 is missing in upstream https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files. Reference: intel/Intel-Linux-Processor-Microcode-Data-Files#62. Use 925555515555 instead of 6c0c4691e5bb. The difference between those two commits are just some "^M" fixes in releasenote.md. Signed-off-by: Yongxin Liu <[email protected]> Signed-off-by: Anuj Mittal <[email protected]>
kraj
pushed a commit
to YoeDistro/meta-intel
that referenced
this issue
Aug 19, 2022
The commit 6c0c4691e5bb446e0e428ebca595164709c59586 is missing in upstream https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files. Reference: intel/Intel-Linux-Processor-Microcode-Data-Files#62. Use 925555515555 instead of 6c0c4691e5bb. The difference between those two commits are just some "^M" fixes in releasenote.md. Signed-off-by: Yongxin Liu <[email protected]> Signed-off-by: Anuj Mittal <[email protected]> (cherry picked from commit a29a3b5) Signed-off-by: Anuj Mittal <[email protected]>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this issue
May 22, 2024
The commit 6c0c4691e5bb446e0e428ebca595164709c59586 is missing in upstream https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files. Reference: intel/Intel-Linux-Processor-Microcode-Data-Files#62. Use 925555515555 instead of 6c0c4691e5bb. The difference between those two commits are just some "^M" fixes in releasenote.md. Signed-off-by: Yongxin Liu <[email protected]> Signed-off-by: Anuj Mittal <[email protected]>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this issue
May 22, 2024
The commit 6c0c4691e5bb446e0e428ebca595164709c59586 is missing in upstream https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files. Reference: intel/Intel-Linux-Processor-Microcode-Data-Files#62. Use 925555515555 instead of 6c0c4691e5bb. The difference between those two commits are just some "^M" fixes in releasenote.md. Signed-off-by: Yongxin Liu <[email protected]> Signed-off-by: Anuj Mittal <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: