From: Andrew Gerrand Date: Wed, 10 Dec 2014 00:01:55 +0000 (+1100) Subject: [release-branch.go1.4] [release-branch.go1.4] doc: scrub references to code.google.com X-Git-Tag: go1.4~6 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=9820fbcf7b256a3d696502888d9b2197a9497dda;p=gostls13.git [release-branch.go1.4] [release-branch.go1.4] doc: scrub references to code.google.com These are the references that affect current Go users. I left intact references in older release notes; we can figure out what to do with them later. LGTM=rsc R=rsc CC=golang-codereviews https://golang.org/cl/186140043 --- diff --git a/doc/code.html b/doc/code.html index ce9f8636fa..a4638f9ffb 100644 --- a/doc/code.html +++ b/doc/code.html @@ -578,7 +578,7 @@ import "github.com/golang/example/stringutil"

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

@@ -627,5 +627,5 @@ The official mailing list for discussion of the Go language is

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

diff --git a/doc/contrib.html b/doc/contrib.html index 8a674d647c..93a609fb20 100644 --- a/doc/contrib.html +++ b/doc/contrib.html @@ -50,7 +50,7 @@ Go 1 matures.

Developer Resources

-

Source Code

+

Source Code

Check out the Go source code.

Developer and @@ -76,13 +76,13 @@ systems and architectures.

How you can help

-

Reporting issues

+

Reporting issues

If you spot bugs, mistakes, or inconsistencies in the Go project's code or documentation, please let us know by -filing a ticket -on our issue tracker. +filing a ticket +on our issue tracker. (Of course, you should check it's not an existing issue before creating a new one.)

@@ -101,8 +101,8 @@ To get started, read these contribution guidelines for information on design, testing, and our code review process.

-Check the tracker for +Check the tracker for open issues that interest you. Those labeled -HelpWanted +helpwanted are particularly in need of outside help.

diff --git a/doc/devel/release.html b/doc/devel/release.html index 1a84391345..1c82e95d55 100644 --- a/doc/devel/release.html +++ b/doc/devel/release.html @@ -3,8 +3,7 @@ }-->

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

+The change log has the full details.

To update to a specific release, use:

diff --git a/doc/devel/weekly.html b/doc/devel/weekly.html index 34c87dc64f..5a9c51ef1d 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 change log and development mailing list.

2012-03-27 (Go 1)

diff --git a/doc/go1.3.html b/doc/go1.3.html index 042de1bc7b..d51052b2e5 100644 --- a/doc/go1.3.html +++ b/doc/go1.3.html @@ -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.4.html b/doc/go1.4.html index 883352e34f..0e9457a28c 100644 --- a/doc/go1.4.html +++ b/doc/go1.4.html @@ -535,7 +535,7 @@ editor, even for editors we do not use. The Go community at large is much better suited to managing this information. In Go 1.4, therefore, this support has been removed from the repository. Instead, there is a curated, informative list of what's available on -a wiki page. +a wiki page.

Performance

diff --git a/doc/go_faq.html b/doc/go_faq.html index 7597997798..6b77f1c1ed 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -228,7 +228,7 @@ document server running in a production configuration on

-Other examples include the Vitess +Other examples include the Vitess system for large-scale SQL installations and Google's download server, dl.google.com, which delivers Chrome binaries and other large installables such as apt-get packages. @@ -986,32 +986,6 @@ See the document for more information about how to proceed.

-

-Why does the project use Mercurial and not git?

- -

-The Go project, hosted by Google Code at -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. -

- -

-Programmers who work -with the Go project's source rather than release downloads sometimes -ask for the project to switch to git. -That would be possible, but it would be a lot of work and -would also require reimplementing the codereview plugin. -Given that Mercurial works today, with code review support, -combined with the Go project's mostly linear, non-branching use of -version control, a switch to git doesn't seem worthwhile. -

-

Why does "go get" use HTTPS when cloning a repository?

diff --git a/doc/help.html b/doc/help.html index a307b2aadd..2cc47806c5 100644 --- a/doc/help.html +++ b/doc/help.html @@ -24,7 +24,7 @@ Need help with Go? Try these resources.

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

Go IRC Channel