From f043963a4a41dee9315dc31b637e4690f2263e0a Mon Sep 17 00:00:00 2001
From: Trevor Miranda <trevor.miranda@protonmail.com>
Date: Wed, 13 Feb 2019 18:31:01 -0500
Subject: [PATCH] Update README to reflect deprecation of cURL.

---
 README.md | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index ff89ca58fff..10c366bac71 100644
--- a/README.md
+++ b/README.md
@@ -530,9 +530,16 @@ If you need a more complex setup, rustup supports the convention used by
 the __curl__ program, documented in the ENVIRONMENT section of
 [its manual page][curlman].
 
-Note that some versions of `libcurl` apparently require you to drop the 
-`http://` or `https://` prefix in environment variables. For example, 
-`export http_proxy=proxy.example.com:1080` (and likewise for HTTPS). 
+The use of `curl` is presently **deprecated**, however it can still be used by
+providing the `RUSTUP_USE_CURL` environment variable, for example:
+
+```
+RUSTUP_USE_CURL=1 rustup update
+```
+
+Note that some versions of `libcurl` apparently require you to drop the
+`http://` or `https://` prefix in environment variables. For example,
+`export http_proxy=proxy.example.com:1080` (and likewise for HTTPS).
 If you are getting an SSL `unknown protocol` error from `rustup` via `libcurl`
 but the command-line `curl` command works fine, this may be the problem.