From 43ad89d627ece6d95529a51eeba67b8748039103 Mon Sep 17 00:00:00 2001 From: Andrew Gerrand Date: Fri, 25 Jul 2014 10:28:39 +1000 Subject: [PATCH] doc: drop scheme from links that are known to support HTTPS golang.org now serves HTTPS with a valid cert, so it's reasonable that users should click through to the HTTPS versions of *.golang.org and other known sites. LGTM=bradfitz R=golang-codereviews, bradfitz CC=golang-codereviews https://golang.org/cl/112650043 --- doc/cmd.html | 6 ++-- doc/code.html | 16 +++++----- doc/contrib.html | 10 +++--- doc/devel/release.html | 66 +++++++++++++++++++-------------------- doc/devel/weekly.html | 2 +- doc/docs.html | 16 +++++----- doc/effective_go.html | 8 ++--- doc/gccgo_contribute.html | 6 ++-- doc/go1.1.html | 2 +- doc/go1.2.html | 10 +++--- doc/go1.3.html | 14 ++++----- doc/go1.html | 12 +++---- doc/go1compat.html | 2 +- doc/go_faq.html | 38 +++++++++++----------- doc/go_spec.html | 2 +- doc/help.html | 8 ++--- doc/install-source.html | 14 ++++----- doc/install.html | 4 +-- doc/root.html | 8 ++--- doc/tos.html | 4 +-- 20 files changed, 124 insertions(+), 124 deletions(-) diff --git a/doc/cmd.html b/doc/cmd.html index b8bdcdadecc..725666f1de5 100644 --- a/doc/cmd.html +++ b/doc/cmd.html @@ -62,7 +62,7 @@ details. -cover +cover      Cover is a program for creating and analyzing the coverage profiles generated by "go test -coverprofile". @@ -83,13 +83,13 @@ gofmt command with more general options. -godoc +godoc      Godoc extracts and generates documentation for Go packages. -vet +vet      Vet examines Go source code and reports suspicious constructs, such as Printf calls whose arguments do not align with the format string. diff --git a/doc/code.html b/doc/code.html index 0abe6ac748c..f019306fa28 100644 --- a/doc/code.html +++ b/doc/code.html @@ -18,7 +18,7 @@ It explains the simplest way to get up and running with your Go installation.

A similar explanation is available as a -screencast. +screencast.

@@ -508,7 +508,7 @@ revision control system such as Git or Mercurial. The go tool uses this property to automatically fetch packages from remote repositories. For instance, the examples described in this document are also kept in a Mercurial repository hosted at Google Code, -code.google.com/p/go.example. +code.google.com/p/go.example. If you include the repository URL in the package's import path, go get will fetch, build, and install it automatically:

@@ -569,8 +569,8 @@ import "code.google.com/p/go.example/newmath"

This convention is the easiest way to make your Go packages available for others to use. -The Go Wiki -and godoc.org +The Go Wiki +and godoc.org provide lists of external Go projects.

@@ -584,7 +584,7 @@ For more information on using remote repositories with the go tool,

Subscribe to the -golang-announce +golang-announce mailing list to be notified when a new stable version of Go is released.

@@ -594,7 +594,7 @@ clear, idiomatic Go code.

-Take A Tour of Go to learn the language +Take A Tour of Go to learn the language proper.

@@ -613,10 +613,10 @@ For real-time help, ask the helpful gophers in #go-nuts on the

The official mailing list for discussion of the Go language is -Go Nuts. +Go Nuts.

Report bugs using the -Go issue tracker. +Go issue tracker.

diff --git a/doc/contrib.html b/doc/contrib.html index 6529c91d559..a615fc67a34 100644 --- a/doc/contrib.html +++ b/doc/contrib.html @@ -9,7 +9,7 @@

Go is an open source project developed by a team at -Google and many +Google and many contributors from the open source community.

@@ -17,13 +17,13 @@ Go is an open source project developed by a team at Go is distributed under a BSD-style license.

-

Announcements Mailing List

+

Announcements Mailing List

A low traffic mailing list for important announcements, such as new releases.

We encourage all Go users to subscribe to -golang-announce. +golang-announce.

@@ -72,9 +72,9 @@ href="https://groups.google.com/group/golang-nuts">golang-nuts.

A mailing list that receives a message summarizing each checkin to the Go repository.

Bugs Mailing List

-

A mailing list that receives each update to the Go issue tracker.

+

A mailing list that receives each update to the Go issue tracker.

-

Build Status

+

Build Status

View the status of Go builds across the supported operating systems and architectures.

diff --git a/doc/devel/release.html b/doc/devel/release.html index 3a3d5bc136a..0824463f4cd 100644 --- a/doc/devel/release.html +++ b/doc/devel/release.html @@ -3,7 +3,7 @@ }-->

This page summarizes the changes between official stable releases of Go. -The Mercurial change log +The Mercurial change log has the full details.

To update to a specific release, use:

@@ -31,12 +31,12 @@ Read the Go 1.2 Release Notes for more information.

go1.2.1 (released 2014/03/02) includes bug fixes to the runtime, net, and database/sql packages. -See the change history for details. +See the change history for details.

go1.2.2 (released 2014/05/05) includes a -security fix +security fix that affects the tour binary included in the binary distributions (thanks to Guillaume T).

@@ -51,18 +51,18 @@ Read the Go 1.1 Release Notes for more information.

go1.1.1 (released 2013/06/13) includes several compiler and runtime bug fixes. -See the change history for details. +See the change history for details.

go1.1.2 (released 2013/08/13) includes fixes to the gc compiler and cgo, and the bufio, runtime, syscall, and time packages. -See the change history for details. +See the change history for details. If you use package syscall's Getrlimit and Setrlimit functions under Linux on the ARM or 386 architectures, please note change -55ac276af5a7 -that fixes issue 5949. +55ac276af5a7 +that fixes issue 5949.

go1 (released 2012/03/28)

@@ -88,17 +88,17 @@ The go1 release corresponds to

go1.0.1 (released 2012/04/25) was issued to -fix an -escape analysis -bug that can lead to memory corruption. +fix an +escape analysis bug +that can lead to memory corruption. It also includes several minor code and documentation fixes.

go1.0.2 (released 2012/06/13) was issued to fix two bugs in the implementation of maps using struct or array keys: -issue 3695 and -issue 3573. +issue 3695 and +issue 3573. It also includes many minor code and documentation fixes.

@@ -107,7 +107,7 @@ go1.0.3 (released 2012/09/21) includes minor code and documentation fixes.

-See the go1 release branch history for the complete list of changes. +See the go1 release branch history for the complete list of changes.

r60 (released 2011/09/07)

@@ -119,7 +119,7 @@ This section highlights the most significant changes in this release. For a more detailed summary, see the weekly release notes. For complete information, see the -Mercurial change list. +Mercurial change list.

Language

@@ -189,26 +189,26 @@ more accessible.

r60.1 includes a -linker +linker fix, a pair of -goplay -fixes, +goplay +fixes, and a json package -fix and +fix and a new -struct tag +struct tag option.

r60.2 -fixes +fixes a memory leak involving maps.

r60.3 fixes a -reflect bug. +reflect bug.

r59 (released 2011/08/01)

@@ -220,7 +220,7 @@ This section highlights the most significant changes in this release. For a more detailed summary, see the weekly release notes. For complete information, see the -Mercurial change list. +Mercurial change list.

Language

@@ -230,7 +230,7 @@ This release includes a language change that restricts the use of goto. In essence, a goto statement outside a block cannot jump to a label inside that block. Your code may require changes if it uses goto. -See this +See this changeset for how the new rule affected the Go tree.

@@ -328,13 +328,13 @@ This section highlights the most significant changes in this release. For a more detailed summary, see the weekly release notes. For complete information, see the -Mercurial change list. +Mercurial change list.

Language

-This release fixes a use of uninitialized memory in programs that misuse goto. +This release fixes a use of uninitialized memory in programs that misuse goto.

Packages

@@ -393,8 +393,8 @@ the Go tree (and avoid writing Makefiles).

Minor revisions

r58.1 adds -build and -runtime +build and +runtime changes to make Go run on OS X 10.7 Lion.

@@ -408,7 +408,7 @@ This section highlights the most significant changes in this release. For a more detailed summary, see the weekly release notes. For complete information, see the -Mercurial change list. +Mercurial change list.

The new gofix tool finds Go programs that use old APIs and rewrites them to use @@ -419,7 +419,7 @@ future changes to the libraries. Gofix can’t handle all situations perfectly, so read and test the changes it makes before committing them. -See the gofix blog post for more +See the gofix blog post for more information.

Language

@@ -465,7 +465,7 @@ For clients, there are new Client and Transport abstractions that give more control over HTTP details such as headers sent and redirections followed. These abstractions make it easy to implement -custom clients that add functionality such as OAuth2. +custom clients that add functionality such as OAuth2. For servers, ResponseWriter has dropped its non-essential methods. The Hijack and Flush methods are no longer required; @@ -509,7 +509,7 @@ implements all the possible value methods. Instead of a type switch on a Value v, switch on v.Kind(). Typeof and NewValue are now called TypeOf and ValueOf To create a writable Value, use New(t).Elem() instead of Zero(t). -See the change description +See the change description for the full details. The new API allows a more efficient implementation of Value that avoids many of the allocations required by the previous API. @@ -545,8 +545,8 @@ For other uses, see the runtime/pprof document

Minor revisions

-

r57.1 fixes a nil pointer dereference in http.FormFile.

-

r57.2 fixes a use of uninitialized memory in programs that misuse goto.

+

r57.1 fixes a nil pointer dereference in http.FormFile.

+

r57.2 fixes a use of uninitialized memory in programs that misuse goto.

r56 (released 2011/03/16)

diff --git a/doc/devel/weekly.html b/doc/devel/weekly.html index c22064258c4..34c87dc64fd 100644 --- a/doc/devel/weekly.html +++ b/doc/devel/weekly.html @@ -5,7 +5,7 @@

This page summarizes the changes between tagged weekly snapshots of Go. Such snapshots are no longer created. This page remains as a historical reference only.

-

For recent information, see the Mercurial change log and development mailing list.

+

For recent information, see the Mercurial change log and development mailing list.

2012-03-27 (Go 1)

diff --git a/doc/docs.html b/doc/docs.html index 1a3d88b4bf3..7eb3a3ad263 100644 --- a/doc/docs.html +++ b/doc/docs.html @@ -33,20 +33,20 @@ libraries. -

A Tour of Go

+

A Tour of Go

An interactive introduction to Go in three sections. The first section covers basic syntax and data structures; the second discusses methods and interfaces; and the third introduces Go's concurrency primitives. Each section concludes with a few exercises so you can practice what you've -learned. You can take the tour online or -install it locally. +learned. You can take the tour online or +install it locally.

How to write Go code

Also available as a -screencast, this doc +screencast, this doc explains how to use the go command to fetch, build, and install packages, commands, and run tests.

@@ -103,7 +103,7 @@ same variable in a different goroutine.

Articles

-

The Go Blog

+

The Go Blog

The official blog of the Go project, featuring news and in-depth articles by the Go team and guests.

@@ -169,17 +169,17 @@ interfaces, reflection, and concurrency. Builds a toy web crawler to demonstrate these.

-

Code that grows with grace

+

Code that grows with grace

One of Go's key design goals is code adaptability; that it should be easy to take a simple design and build upon it in a clean and natural way. In this talk Andrew Gerrand describes a simple "chat roulette" server that matches pairs of incoming TCP connections, and then use Go's concurrency mechanisms, interfaces, and standard library to extend it with a web interface and other features. While the function of the program changes dramatically, Go's flexibility preserves the original design as it grows.

-

Go Concurrency Patterns

+

Go Concurrency Patterns

Concurrency is the key to designing high performance network services. Go's concurrency primitives (goroutines and channels) provide a simple and efficient means of expressing concurrent execution. In this talk we see how tricky concurrency problems can be solved gracefully with simple Go code.

-

Advanced Go Concurrency Patterns

+

Advanced Go Concurrency Patterns

This talk expands on the Go Concurrency Patterns talk to dive deeper into Go's concurrency primitives.

diff --git a/doc/effective_go.html b/doc/effective_go.html index 25266d6abac..c1e310796be 100644 --- a/doc/effective_go.html +++ b/doc/effective_go.html @@ -28,7 +28,7 @@ will be easy for other Go programmers to understand.

This document gives tips for writing clear, idiomatic Go code. It augments the language specification, -the Tour of Go, +the Tour of Go, and How to Write Go Code, all of which you should read first. @@ -43,8 +43,8 @@ only as the core library but also as examples of how to use the language. Moreover, many of the packages contain working, self-contained executable examples you can run directly from the -golang.org web site, such as -this one (if +golang.org web site, such as +this one (if necessary, click on the word "Example" to open it up). If you have a question about how to approach a problem or how something might be implemented, the documentation, code and examples in the @@ -3214,7 +3214,7 @@ Although the concurrency features of Go can make some problems easy to structure as parallel computations, Go is a concurrent language, not a parallel one, and not all parallelization problems fit Go's model. For a discussion of the distinction, see the talk cited in -this +this blog post.

A leaky buffer

diff --git a/doc/gccgo_contribute.html b/doc/gccgo_contribute.html index ad2ce46ac93..9dd6ecb8521 100644 --- a/doc/gccgo_contribute.html +++ b/doc/gccgo_contribute.html @@ -30,7 +30,7 @@ contribution rules.

The master sources for the gccgo frontend may be found at -http://code.google.com/p/gofrontend. +http://code.google.com/p/gofrontend. The master sources are not buildable by themselves, but only in conjunction with GCC (in the future, other compilers may be supported). Changes made to the gccgo frontend are also applied to @@ -40,7 +40,7 @@ is mirrored to the gcc/go/gofrontend directory in the GCC repository, and the gofrontend libgo directory is mirrored to the GCC libgo directory. In addition, the test directory -from the main Go repository +from the main Go repository is mirrored to the gcc/testsuite/go.test/test directory in the GCC repository.

@@ -65,7 +65,7 @@ from gcc/go/gofrontend to gcc/go.

The run-time library for gccgo is mostly the same as the library -in the main Go repository. +in the main Go repository. The library code in the Go repository is periodically merged into the libgo/go directory of the gofrontend and then the GCC repositories, using the shell diff --git a/doc/go1.1.html b/doc/go1.1.html index 87d5f5c8768..825867f4420 100644 --- a/doc/go1.1.html +++ b/doc/go1.1.html @@ -304,7 +304,7 @@ The race detector is documented in a

Due to the change of the int to 64 bits and -a new internal representation of functions, +a new internal representation of functions, the arrangement of function arguments on the stack has changed in the gc tool chain. Functions written in assembly will need to be revised at least to adjust frame pointer offsets. diff --git a/doc/go1.2.html b/doc/go1.2.html index c7a9f844264..b9d36f29c3d 100644 --- a/doc/go1.2.html +++ b/doc/go1.2.html @@ -63,7 +63,7 @@ The implementation may inject extra tests into the compiled program to enforce t

Further details are in the -design document. +design document.

@@ -115,7 +115,7 @@ It is possible that future releases of Go may introduce default values for these

Further details are in the -design document. +design document.

@@ -199,7 +199,7 @@ compiler to build any pieces of the linked-to library that are written in C++;

Both binaries are still included with the distribution, but the source code for the godoc and vet commands has moved to the -go.tools subrepository. +go.tools subrepository.

@@ -218,7 +218,7 @@ no client Go code depends on the their source and no updating is required.

-The binary distributions available from golang.org +The binary distributions available from golang.org include these binaries, so users of these distributions are unaffected.

@@ -448,7 +448,7 @@ The new interfaces are called and TextUnmarshaler. Full details are in the documentation for the package -and a separate design document. +and a separate design document.

The fmt package

diff --git a/doc/go1.3.html b/doc/go1.3.html index ae5c0259859..0d2bda122d8 100644 --- a/doc/go1.3.html +++ b/doc/go1.3.html @@ -66,7 +66,7 @@ It runs on the 32-bit Intel architectures (GOARCH=386) and also on There is not yet support for Native Client on ARM. Note that this is Native Client (NaCl), not Portable Native Client (PNaCl). Details about Native Client are here; -how to set up the Go version is described here. +how to set up the Go version is described here.

Support for NetBSD

@@ -118,7 +118,7 @@ than is available, its stack is transferred to a larger single block of memory. The overhead of this transfer operation amortizes well and eliminates the old "hot spot" problem when a calculation repeatedly steps across a segment boundary. Details including performance numbers are in this -design document. +design document.

Changes to the garbage collector

@@ -141,7 +141,7 @@ Programs that use package unsafe to store pointers in integer-typed values are also illegal but more difficult to diagnose during execution. Because the pointers are hidden from the runtime, a stack expansion or garbage collection may reclaim the memory they point at, creating -dangling pointers. +dangling pointers.

@@ -154,7 +154,7 @@ Such code can be identified by go vet.

Iterations over small maps no longer happen in a consistent order. -Go 1 defines that “The iteration order over maps +Go 1 defines that “The iteration order over maps is not specified and is not guaranteed to be the same from one iteration to the next.” To keep code from depending on map iteration order, Go 1.0 started each map iteration at a random index in the map. @@ -175,7 +175,7 @@ Because only small maps are affected, the problem arises most often in tests.

-As part of the general overhaul to +As part of the general overhaul to the Go linker, the compilers and linkers have been refactored. The linker is still a C program, but now the instruction selection phase that was part of the linker has been moved to the compiler through the creation of a new @@ -298,7 +298,7 @@ For example,

Changes to godoc

When invoked with the -analysis flag, -godoc +godoc now performs sophisticated static analysis of the code it indexes. The results of analysis are presented in both the source view and the @@ -318,7 +318,7 @@ call sites and their callees. The program misc/benchcmp that compares performance across benchmarking runs has been rewritten. Once a shell and awk script in the main repository, it is now a Go program in the go.tools repo. -Documentation is here. +Documentation is here.

diff --git a/doc/go1.html b/doc/go1.html index a664b655553..5cf5df9296a 100644 --- a/doc/go1.html +++ b/doc/go1.html @@ -486,7 +486,7 @@ into subdirectories. For instance, utf8 and utf16 now occupy subdirectories of unicode. Also, some packages have moved into subrepositories of -code.google.com/p/go +code.google.com/p/go while others have been deleted outright.

@@ -565,7 +565,7 @@ by hand.

Because they are not standardized, the packages under the exp directory will not be available in the standard Go 1 release distributions, although they will be available in source code form -in the repository for +in the repository for developers who wish to use them.

@@ -651,7 +651,7 @@ and also the command gotry. Updating: Code that uses container/vector should be updated to use slices directly. See -the Go +the Go Language Community Wiki for some suggestions. Code that uses the other packages (there should be almost zero) will need to be rethought.

@@ -660,7 +660,7 @@ Code that uses the other packages (there should be almost zero) will need to be

Go 1 has moved a number of packages into other repositories, usually sub-repositories of -the main Go repository. +the main Go repository. This table lists the old and new import paths: @@ -1695,7 +1695,7 @@ The compiler will catch code using the old interface. The regexp package has been rewritten. It has the same interface but the specification of the regular expressions it supports has changed from the old "egrep" form to that of -RE2. +RE2.

@@ -1912,7 +1912,7 @@ package reflect. Updating: Code using these functions must be rewritten to use package reflect. -The changes to encoding/gob and the protocol buffer library +The changes to encoding/gob and the protocol buffer library may be helpful as examples.

diff --git a/doc/go1compat.html b/doc/go1compat.html index 7ca3d355d64..d10b9af2947 100644 --- a/doc/go1compat.html +++ b/doc/go1compat.html @@ -145,7 +145,7 @@ developed software based on Go 1.

Code in sub-repositories of the main go tree, such as -code.google.com/p/go.net, +code.google.com/p/go.net, may be developed under looser compatibility requirements. However, the sub-repositories will be tagged as appropriate to identify versions that are compatible diff --git a/doc/go_faq.html b/doc/go_faq.html index b1945dda830..f2082ef5b22 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -57,7 +57,7 @@ software on multicore machines.

A much more expansive answer to this question is available in the article, -Go at Google: +Go at Google: Language Design in the Service of Software Engineering.

@@ -66,7 +66,7 @@ What is the status of the project?

Go became a public open source project on November 10, 2009. After a couple of years of very active design and development, stability was called for and -Go 1 was released +Go 1 was released on March 28, 2012. Go 1, which includes a language specification, standard libraries, @@ -163,7 +163,7 @@ language was called for.

-The article Go at Google +The article Go at Google discusses the background and motivation behind the design of the Go language, as well as providing more detail about many of the answers presented in this FAQ.

@@ -221,7 +221,7 @@ easier to understand what happens when things combine.

Yes. There are now several Go programs deployed in production inside Google. A public example is the server behind -http://golang.org. +golang.org. It's just the godoc document server running in a production configuration on Google App Engine. @@ -260,7 +260,7 @@ Does Go support Google's protocol buffers?

A separate open source project provides the necessary compiler plugin and library. It is available at -http://code.google.com/p/goprotobuf/ +code.google.com/p/goprotobuf/

@@ -270,9 +270,9 @@ Can I translate the Go home page into another language?

Absolutely. We encourage developers to make Go Language sites in their own languages. However, if you choose to add the Google logo or branding to your site -(it does not appear on golang.org), +(it does not appear on golang.org), you will need to abide by the guidelines at -http://www.google.com/permissions/guidelines.html +www.google.com/permissions/guidelines.html

Design

@@ -466,7 +466,7 @@ Will you accept my language change?

People often suggest improvements to the language—the -mailing list +mailing list contains a rich history of such discussions—but very few of these changes have been accepted.

@@ -484,7 +484,7 @@ to start talking about what that might be.

Even if your proposal is compatible with the Go 1 spec, it might not be in the spirit of Go's design goals. -The article Go +The article Go at Google: Language Design in the Service of Software Engineering explains Go's origins and the motivation behind its design.

@@ -940,9 +940,9 @@ How are libraries documented? There is a program, godoc, written in Go, that extracts package documentation from the source code. It can be used on the command line or on the web. An instance is running at -http://golang.org/pkg/. +golang.org/pkg/. In fact, godoc implements the full site at -http://golang.org/. +golang.org/.

@@ -961,7 +961,7 @@ All the Go code in the repository has been run through gofmt.

The document titled -Go Code Review Comments +Go Code Review Comments is a collection of very short essays about details of Go idiom that are often missed by programmers. It is a handy reference for people doing code reviews for Go projects. @@ -986,14 +986,14 @@ Why does the project use Mercurial and not git?

The Go project, hosted by Google Code at -code.google.com/p/go, +code.google.com/p/go, uses Mercurial as its version control system. When the project launched, Google Code supported only Subversion and Mercurial. Mercurial was a better choice because of its plugin mechanism that allowed us to create the "codereview" plugin to connect the project to the excellent code review tools at -codereview.appspot.com. +codereview.appspot.com.

@@ -1304,7 +1304,7 @@ Do not communicate by sharing memory. Instead, share memory by communicating.

-See the Share Memory By Communicating code walk and its associated article for a detailed discussion of this concept. +See the Share Memory By Communicating code walk and its associated article for a detailed discussion of this concept.

@@ -1321,7 +1321,7 @@ run-time support to utilize more than one OS thread. Programs that perform parallel computation should benefit from an increase in GOMAXPROCS. However, be aware that -concurrency +concurrency is not parallelism.

@@ -1358,7 +1358,7 @@ should recognize such cases and optimize its use of OS threads. For now,

For more detail on this topic see the talk entitled, -Concurrency +Concurrency is not Parallelism.

Functions and Methods

@@ -1736,7 +1736,7 @@ In any case, Go can often be very competitive. There has been significant improvement in the performance of many programs as the language and tools have developed. See the blog post about -profiling +profiling Go programs for an informative example.

Changes from C

@@ -1895,7 +1895,7 @@ considerable control over memory layout and allocation, much more than is typical in garbage-collected languages. A careful programmer can reduce the garbage collection overhead dramatically by using the language well; see the article about -profiling +profiling Go programs for a worked example, including a demonstration of Go's profiling tools.

diff --git a/doc/go_spec.html b/doc/go_spec.html index 88323753780..0200762dcc0 100644 --- a/doc/go_spec.html +++ b/doc/go_spec.html @@ -23,7 +23,7 @@ TODO

This is a reference manual for the Go programming language. For -more information and other documents, see http://golang.org. +more information and other documents, see golang.org.

diff --git a/doc/help.html b/doc/help.html index ad92c5695bd..a307b2aadd7 100644 --- a/doc/help.html +++ b/doc/help.html @@ -20,11 +20,11 @@ Need help with Go? Try these resources.

The Go Wiki

A wiki maintained by the Go community.

-

Go Nuts Mailing List

+

Go Nuts Mailing List

-Search the golang-nuts +Search the golang-nuts archives and consult the FAQ and -wiki before posting. +wiki before posting.

Go IRC Channel

@@ -37,7 +37,7 @@ Go IRC channel.

The Go Programming Language at Google+

The Go project's Google+ page.

-

@golang at Twitter

+

@golang at Twitter

The Go project's official Twitter account.

Tweeting about your problem with the #golang hashtag usually generates some helpful responses.

diff --git a/doc/install-source.html b/doc/install-source.html index 6f6a15afda4..82859b50fb5 100644 --- a/doc/install-source.html +++ b/doc/install-source.html @@ -81,7 +81,7 @@ The full set of supported combinations is listed in the discussion of

The Go tool chain is written in C. To build it, you need a C compiler installed. -Please refer to the InstallFromSource +Please refer to the InstallFromSource page on the Go community Wiki for operating system specific instructions.

@@ -283,16 +283,16 @@ You can access the latter commands with The usual community resources such as #go-nuts on the Freenode IRC server and the -Go Nuts +Go Nuts mailing list have active developers that can help you with problems with your installation or your development work. For those who wish to keep up to date, -there is another mailing list, golang-checkins, +there is another mailing list, golang-checkins, that receives a message summarizing each checkin to the Go repository.

-Bugs can be reported using the Go issue tracker. +Bugs can be reported using the Go issue tracker.

@@ -306,7 +306,7 @@ The Go project maintains a stable tag in its Mercurial repository:

The release tag refers to the current stable release of Go. Most Go users should use this version. New releases are announced on the -golang-announce +golang-announce mailing list.

@@ -482,8 +482,8 @@ should target. If you are compiling on the target system, its value will be auto

If in doubt, leave this variable unset, and adjust it if required when you first run the Go executable. -The GoARM page -on the Go community wiki +The GoARM page +on the Go community wiki contains further details regarding Go's ARM support.

diff --git a/doc/install.html b/doc/install.html index 7282ae94728..2de04471c5e 100644 --- a/doc/install.html +++ b/doc/install.html @@ -270,12 +270,12 @@ For real-time help, ask the helpful gophers in #go-nuts on the

The official mailing list for discussion of the Go language is -Go Nuts. +Go Nuts.

Report bugs using the -Go issue tracker. +Go issue tracker.

diff --git a/doc/root.html b/doc/root.html index 43637933a65..3c6de2e46c7 100644 --- a/doc/root.html +++ b/doc/root.html @@ -26,7 +26,7 @@ Hello, 世界
Run -Tour +Tour