add disclaimer about the move to nim-lang/bigints #39
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
Member
|
How about I move my repo to nim-lang/bigints using the github settings instead? Then everyone landing in def-/nim-bigints would automatically be redirected to nim-lang/bigints. |
Contributor
Author
ah, yes, I agree it would be a better option (stars would also be inherited), but it would require some additional effort on aligning the repo. nim-lang/bigints was forked some time ago and commit history diverged. I think the effort would be worth though. I will close this PR now (we can always open it again) and we could probably move this discussion on nim-lang/Nim#14696 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Might I add here big thanks 🙏 to @def- for this, we miss you in Nim community! 😊
nim-lang/Nim#14696 (comment)