cp --remove-destination: don't fail if destination is hardlink to source #5431
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
cakebaker
force-pushed
the
cp_remove_destination_shouldnt_fail_hardlink
branch
2 times, most recently
from
7c7e822 to
04dec5c
Compare
sylvestre
force-pushed
the
cp_remove_destination_shouldnt_fail_hardlink
branch
from
04dec5c to
94492c9
Compare
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.
With this PR, cp --remove-destination no longer shows an error on Unix platforms if the destination is a hardlink to the source and the destination is removed instead.
This PR probably conflicts with #5430