diff options
author | Rob Pike <r@golang.org> | 2012-09-22 05:55:04 +1000 |
---|---|---|
committer | Rob Pike <r@golang.org> | 2012-09-22 05:55:04 +1000 |
commit | 094cd0c1b3634bfab2206fa15ae6e6975ac7f85a (patch) | |
tree | f8094315bd2ce7c352bb547524ccafa8281b8b22 | |
parent | 807da621f683b4c1ba89fe55660013576267bd9c (diff) | |
download | go-094cd0c1b3634bfab2206fa15ae6e6975ac7f85a.tar.gz |
[release-branch.go1] faq: mercurial vs. git
??? backport 4a9c3b3e39c6
faq: mercurial vs. git
Fixes issue 4052.
R=golang-dev, bradfitz, iant, rsc
CC=golang-dev
http://codereview.appspot.com/6490092
???
-rw-r--r-- | doc/go_faq.html | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/go_faq.html b/doc/go_faq.html index ea6edc37e..64acd96a2 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -922,6 +922,32 @@ See the document for more information about how to proceed. </p> +<h3 id="Why_does_the_project_use_Mercurial_and_not_git"> +Why does the project use Mercurial and not git?</h3> + +<p> +The Go project, hosted by Google Code at +<a href="http://code.google.com/p/go">code.google.com/p/go</a>, +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 +<a href="http://codereview.appspot.com">codereview.appspot.com</a>. +</p> + +<p> +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. +</p> + <h2 id="Pointers">Pointers and Allocation</h2> <h3 id="pass_by_value"> |