Clarify preferred btrfs-progs dependency and fix some minor inconsistencies #9756
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.
cc @vbatts
There's been some confusion here thinking that 3.8 is fine and that 3.16 should not be preferred (and that specifying
btrfs_noversion
is "OK" even with 3.16+), so I've rewritten this bit to hopefully clarify that we do in fact prefer 3.16.1+ and that lower versions are highly discouraged but supported where necessary.