From efc7460c787535c46feadda9f7c395f16a615306 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Mon, 26 Mar 2018 11:39:27 -0400 Subject: content/versioning-proposal: fix two links Change-Id: Ife215c4731452cea39431b8b63abef570be14697 Reviewed-on: https://go-review.googlesource.com/102596 Run-TryBot: Russ Cox Reviewed-by: Russ Cox --- content/versioning-proposal.article | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'content/versioning-proposal.article') diff --git a/content/versioning-proposal.article b/content/versioning-proposal.article index 20c4426..f6dd1d6 100644 --- a/content/versioning-proposal.article +++ b/content/versioning-proposal.article @@ -49,7 +49,7 @@ made developers feel much more comfortable relying on Go for production use and is a key reason that Go is popular today. Since 2013 the -[[https://golang.org/doc/faq][Go FAQ]] +[[https://golang.org/doc/faq#get_version][Go FAQ]] has encouraged package developers to provide their own users with similar expectations of compatibility. We call this the _import_compatibility_rule_: @@ -251,7 +251,7 @@ which I filed last week. Even though it might look like a complete implementation, it’s still just a prototype, one that we will all need to work together to complete. -You can download and try the `vgo` prototype from [[golang.org/x/vgo][https://golang.org/x/vgo]], +You can download and try the `vgo` prototype from [[https://golang.org/x/vgo][golang.org/x/vgo]], and you can read the [[https://research.swtch.com/vgo-tour][Tour of Versioned Go]] to get a sense of what using `vgo` is like. -- cgit v1.2.3