use the original nim-lang/Nim repo instead of a fork #102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The status-im/Nim fork is not need anymore, since everything needed is getting fixed and backported in a timely manner in the original repo. This removes one layer of indirection and we won't have to do pointless pulls/syncs in our fork before upgrading to a newer Nim version.
tersec
approved these changes
Apr 22, 2025
|
@tersec does this need something more than your approval before merging? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The status-im/Nim fork is not need anymore, since everything needed is getting fixed and backported in a timely manner in the original repo.
This removes one layer of indirection and we won't have to do pointless pulls/syncs in our fork before upgrading to a newer Nim version.