From: Daniel Stenberg <daniel@haxx.se>
Date: Sat, 2 Apr 2016 15:59:25 +0000 (+0200)
Subject: curl.1: -w filename_effective was introduced in 7.26.0
X-Git-Tag: curl-7_49_0~230
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e238253d06199e15f86d860a367b8b9250a7ff7f;p=thirdparty%2Fcurl.git

curl.1: -w filename_effective was introduced in 7.26.0

We never made a 7.25.1 release
---

diff --git a/docs/curl.1 b/docs/curl.1
index f0c941199d..668e385ffe 100644
--- a/docs/curl.1
+++ b/docs/curl.1
@@ -1895,7 +1895,7 @@ The Content-Type of the requested document, if there was any.
 The ultimate filename that curl writes out to. This is only meaningful if curl
 is told to write to a file with the \fI--remote-name\fP or \fI--output\fP
 option. It's most useful in combination with the \fI--remote-header-name\fP
-option. (Added in 7.25.1)
+option. (Added in 7.26.0)
 .TP
 .B ftp_entry_path
 The initial path curl ended up in when logging on to the remote FTP