← Commit list

c6eb9bb3dc

Daniel Stenberg
Daniel Stenberg
2025-11-12
SUCCESS Duration: 143s

Subject

_PROGRESS.md: add the E unit, mention kibibyte

Binary

No binary (build failed)

Architecture & Compiler Flags

Architecture: x86_64-linux-gnu Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04.3) 11.4.0

—

Build Log

(log yok)

Commit Diff GitHub →

.github/scripts/pyspelling.words+3 -0
@@ -244,6 +244,7 @@ et
etag
ETag
ETags
+exa
exe
executables
EXPN
@@ -417,6 +418,7 @@ kerberos
Keychain
keychain
KiB
+kibibyte
kickstart
Kirei
Knauf
@@ -491,6 +493,7 @@ Mavrogiannopoulos
Mbed
mbedTLS
md
+mebibyte
Meglio
memdebug
MesaLink
docs/cmdline-opts/_PROGRESS.md+6 -5
@@ -4,9 +4,10 @@
curl normally displays a progress meter during operations, indicating the
amount of transferred data, transfer speeds and estimated time left, etc. The
-progress meter displays the transfer rate in bytes per second. The suffixes
-(`k` for kilo, `M` for mega, `G` for giga, `T` for tera, and `P` for peta) are
-1024 based. For example 1k is 1024 bytes. 1M is 1048576 bytes.
+progress meter displays the transfer rate in bytes per second. The used
+suffixes (`k` for kilo, `M` for mega, `G` for giga, `T` for tera, `P` for peta
+and `E` for exa) are 1024 based. For example 1k is 1024 bytes. 1M is 1048576
+bytes. Strictly speaking this makes the units kibibyte and mebibyte etc.
curl displays this data to the terminal by default, so if you invoke curl to
do an operation and it is about to write data to the terminal, it *disables*
@@ -14,8 +15,8 @@ the progress meter as otherwise it would mess up the output mixing progress
meter and response data.
If you want a progress meter for HTTP POST or PUT requests, you need to
-redirect the response output to a file, using shell redirect (\>), --output
-or similar.
+redirect the response output to a file, using shell redirect (\>), --output or
+similar.
This does not apply to FTP upload as that operation does not spit out any
response data to the terminal.