isChownNeeded bad when only user/group (!both) set #1652
Merged
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.
isChownNeeded returned the wrong result if either (exclusive) user or group were set but not the other. It uses a guard value but only compares both at the start and doesn't take this into account on the final comparison which compares both against the current values.
IE. it always returns true in these cases as the guard value is never going to be the same as an real file value.
Fixes #1651