btrfs-progs: docs: update the compatibility about compression #1020
+12
−4
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
There is a github issue that expressed confusion about the "Compatibility" section of "ch-compression.rst". The words in the man page is indeed confusing, and some points are no longer correct either. Considering how complex the direct IO and compression thing is, I didn't come up with a correct answer until reading the code. So update that section to provide a more straightforward result. Issue: kdave#1015 Signed-off-by: Qu Wenruo <[email protected]>
|
It looks like there’s a minor typo: I believe the second nodatasum should be nodatacow. |
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.
There is a github issue that expressed confusion about the "Compatibility" section of "ch-compression.rst".
The words in the man page is indeed confusing, and some points are no longer correct either.
Considering how complex the direct IO and compression thing is, I didn't come up with a correct answer until reading the code.
So update that section to provide a more straightforward result.
Issue: #1015