aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShenghou Ma <minux.ma@gmail.com>2013-12-03 08:40:20 +1100
committerAndrew Gerrand <adg@golang.org>2013-12-03 08:40:20 +1100
commit1ba2842eacf74866ffe6f4b11488433d37648ca5 (patch)
treeba51fc74a79631d2194b7f3236d52dd7dc51b033
parent1601cf2af6ed6496b7fa481b640779cf49a492ca (diff)
go.blog/content/cover.article: fix URL
R=adg CC=golang-dev https://golang.org/cl/36250043
-rw-r--r--content/cover.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/cover.article b/content/cover.article
index 0af23f3..4e6bcdb 100644
--- a/content/cover.article
+++ b/content/cover.article
@@ -50,7 +50,7 @@ correct and easy-to-read code.
One example is the gofix tool, which automates the
rewriting of code to use new language features or updated libraries.
Gofix let us make fundamental changes to the language and libraries in the
-[[blog.golang.org/the-path-to-go-1][run-up to Go 1.0]],
+[[http://blog.golang.org/the-path-to-go-1][run-up to Go 1.0]],
with the confidence that users could just run the tool to update their source to the newest version.
Inside Google, we have used gofix to make sweeping changes in a huge code repository that would be almost