Skip to content
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

Revive #140

Merged
merged 5 commits into from
Jan 8, 2025
Merged

Revive #140

merged 5 commits into from
Jan 8, 2025

Conversation

freaz
Copy link
Member

@freaz freaz commented Sep 30, 2024

No description provided.

@freaz freaz changed the title WIP: Revive Revive Dec 17, 2024
@freaz freaz requested a review from TheEdward162 December 17, 2024 14:59
Copy link
Contributor

@TheEdward162 TheEdward162 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

One thing I'm thinking about is that build-a-core might not work with older toolchains because of the target rename (the p1) after this commit. We don't use it currently so that's not an issue, and one can always either edit it manually or switch to an older commit - or maybe in the future we can add some logic to pick the right target based on toolchain version. Just wanted to say it here in case we need it later.

@TheEdward162 TheEdward162 mentioned this pull request Jan 7, 2025
4 tasks
@freaz
Copy link
Member Author

freaz commented Jan 8, 2025

Honestly I didn't think about it. What would be the reason?

@freaz freaz merged commit 0f338ec into main Jan 8, 2025
6 checks passed
@freaz freaz deleted the chore/revive branch January 8, 2025 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants