curl: --continue-at is mutually exclusive with --no-clobber

Test 481 verifies

Fixes #15645
Reported-by: Harry Sintonen
Closes #15668
This commit is contained in:
Daniel Stenberg 2024-12-02 14:07:45 +01:00
parent 26ee83ab67
commit ffbcde0022
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
5 changed files with 60 additions and 1 deletions

View file

@ -27,3 +27,5 @@ transfer. It then uses the given output/input files to figure that out.
This command line option is mutually exclusive with --range: you can only use
one of them for a single transfer.
The --no-clobber option cannot be used together with --continue-at.

View file

@ -24,3 +24,5 @@ create any file.
Note that this is the negated option name documented. You can thus use
--clobber to enforce the clobbering, even if --remote-header-name is
specified.
The --continue-at option cannot be used together with --no-clobber.