Fixed error in README.md regarding usage of the zstd compression type #51
Conversation
This file contains 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 functional argument for using zstd is `-C zst` not `-C zstd`.
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 functional argument for using zstd at the moment in
mkstage4is-C zstnot-C zstd.This is due the fact that the extension for zstd compressed files is
.zst.To account for this, the script could be changed to accept
zstdas compression type (-C), becausezstdis probably the most commonly referred keyword for zstd compression, see e.g.tar --zstd.But for now the script works with
-C zst, so this should be reflected in the documentation/README.