diff options
author | Rob Pike <r@golang.org> | 2012-09-07 11:19:01 -0700 |
---|---|---|
committer | Rob Pike <r@golang.org> | 2012-09-07 11:19:01 -0700 |
commit | 0d975cb94cf9da886e26d90d00849e225572d428 (patch) | |
tree | 5b4db045ac4cd407ed4821d565fc3a8dbbe94b34 /doc/go_faq.html | |
parent | f8d7fc98634e4d6e327bfeb9a51fc8c1c32dcb53 (diff) | |
download | go-0d975cb94cf9da886e26d90d00849e225572d428.tar.gz |
faq: mercurial vs. git
Fixes issue 4052.
R=golang-dev, bradfitz, iant, rsc
CC=golang-dev
http://codereview.appspot.com/6490092
Diffstat (limited to 'doc/go_faq.html')
-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"> |