openkal-musl 0.3.0: continue this repository's version line rather than restart it - #2
Merged
Conversation
…an restart it The package is new and the repository is not. 0.1.0 and 0.2.0 name the earlier package --- openkal-libc, a probe of 243 lines --- in this repository's own tags, which came with it when it was renamed. A version that restarted at 0.1.0 would give one tag two meanings, and a tag is the one thing in the release chain that cannot be given a second meaning. So the name changed at 0.3.0 and the numbers do not go backwards.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 package is new and the repository is not.
0.1.0and0.2.0name theearlier package —
openkal-libc, a probe of 243 lines exporting 14 names — inthis repository's own tags, which came with it when it was renamed.
A version that restarted at
0.1.0would give one tag two meanings, and a tag isthe one thing in the release chain that cannot be given a second meaning: the CN
mirror allows neither replacing an asset nor deleting a release.
So the name changed at
0.3.0and the numbers do not go backwards. The indexkeeps
openkal-libcup to 0.2.0 for anything pinned to it, and carriesopenkal-muslfrom 0.3.0.