[GNUnet-SVN] [gnurl] 67/173: TODO: implemened "--fail-fast to exit on first transfer fail"

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to annotated tag gnurl-7.53.1
in repository gnurl.

commit 535a29c01acc519c7c11e0a50ede9ce1b0b89100
Author: Daniel Stenberg <address@hidden>
AuthorDate: Sat Jan 14 12:42:53 2017 +0100

    TODO: implemened "--fail-fast to exit on first transfer fail"
    
    Even though it is called --fail-early
---
 docs/TODO | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/docs/TODO b/docs/TODO
index 66341c331..84ac48e2f 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -150,8 +150,7 @@
  18.12 keep running, read instructions from pipe/socket
  18.13 support metalink in http headers
  18.14 --fail without --location should treat 3xx as a failure
- 18.15 Introduce --fail-fast to exit on first transfer fail
- 18.16 --retry should resume
+ 18.15 --retry should resume
 
  19. Build
  19.1 roffit
@@ -1012,15 +1011,7 @@ that doesn't exist on the server, just like 
--ftp-create-dirs.
  way to implement this is probably to add that new logic in the command line
  tool only and not in the underlying CURLOPT_FAILONERROR logic.
 
-18.15 Introduce --fail-fast to exit on first transfer fail
-
- curl will transfer all URLs given on the command line one by one but only
- returns the error code for the last transfer. Transfer failures on the first
- ones will not be returned as error code etc to the shell. A --fail-fast
- option would make curl exit and return an error for the first transfer that
- fails.
-
-18.16 --retry should resume
+18.15 --retry should resume
 
  When --retry is used and curl actually retries transfer, it should use the
  already transfered data and do a resumed transfer for the rest (when

-- 
To stop receiving notification emails like this one, please contact
address@hidden