From f2c26bab772e6b69a9fca945534728678578eb2b Mon Sep 17 00:00:00 2001
From: russoj88 <russoj88@gmail.com>
Date: Tue, 13 Aug 2019 21:10:38 -0700
Subject: [PATCH] Rewrite the "pinning to v1" section.

---
 README.md | 19 +++----------------
 1 file changed, 3 insertions(+), 16 deletions(-)

diff --git a/README.md b/README.md
index 29ed171..6748476 100644
--- a/README.md
+++ b/README.md
@@ -108,25 +108,12 @@ import (
 ...
 ```
 
-### Pinning to the `v1` releases
+### Using `v1` releases
 
-Similarly to the section above describing use of the `v2` branch, if one wants
-to avoid any unexpected compatibility pains once `v2` becomes `master`, then
-pinning to `v1` is an acceptable option, e.g.:
+Use the github URL to use the v1 branch.  This is illustrated in the Getting Started section below.
 
-```
-$ go get gopkg.in/urfave/cli.v1
-```
-
-``` go
-...
-import (
-  "gopkg.in/urfave/cli.v1" // imports as package "cli"
-)
-...
-```
+Do not use the gopkg.in URL as it does not work for versions >= 1.21.0.
 
-This will pull the latest tagged `v1` release (e.g. `v1.18.1` at the time of writing).
 
 ## Getting Started