-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix cp --sparse=auto
not creating sparse-files.
#6130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix cp --sparse=auto
not creating sparse-files.
#6130
Conversation
GNU testsuite comparison:
|
these are probably yours |
GNU testsuite comparison:
|
GNU testsuite comparison:
|
Reverting to old behaviour for non sparse files
GNU testsuite comparison:
|
Could you please add tests? |
Added tests . |
GNU testsuite comparison:
|
GNU testsuite comparison:
|
Co-authored-by: Sylvestre Ledru <sylvestre@debian.org>
GNU testsuite comparison:
|
The overall code changes look good to me, but someone else should merge it. In particular, I'm unhappy with squashing it all into a single commit, but I'm also unhappy with 39 fix-fixing commits ^^' EDIT: Also, please see |
Sorry for the bad commit hygiene . Do i do another commit to fix the spelling ? ;( |
commit hygiene: No worries, no damage has been done! :D spelling: Yes, please fix the typo in whatever way you think is best. |
GNU testsuite comparison:
|
Co-authored-by: Sylvestre Ledru <sylvestre@debian.org>
Will let someone else squash , i am too bad at git :( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those EDIT: Nope, they can't be simplified. All is good.match
arms look like they're repeating, and the error types should be compatible. Can this be simplified?
GNU testsuite comparison:
|
Closed in favor of #6220 |
Fixes #6129