New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: install-source.html needs updated instructions. #9529
Comments
The doc is not broken. The latest stable (go1.4) has been released from the Mercurial repo, therefore it's still recommended to install go1.4 from the legacy repo. |
I agree: I think this is correct. The project moved to git after the 1.4 release, and the 1.4 release is still delivered from Mercurial. |
@ianlancetaylor I believe there is still an issue. Following the install from source instructions gets you Go 1.3, not 1.4
|
This will be fixed in 1.4.1. I don't have the patience to figure out why Mercurial is so broken. I'm glad it will all be behind us shortly. |
Very interesting hg behavior. I double checked the tags (go1.4 and release) are correct on the hg clone -u release ... |
@minux very puzzling indeed. I'm curious as to whether it'll work correctly if you |
If i clone from a local repository (in the default branch, with correct hg clone -u /path/to/go go1.4 # this get me to 1.3 branch Only "hg up go1.4" can get me to the 1.4 branch. and there is no release tag in 1.3 branch's .hgtags, so I don't undertand |
As I said, I'm glad this will be behind us soon :-) |
thank you. I was about to type this up, but thought maybe I'm just nitpicking too much. ... oz
|
thanks @davecheney |
@adg sure that works, avoids mentioning lengthy release names. |
The updated instructions are now rolled out to golang.org. |
as of december 10 "This release also coincides with the project's move from Mercurial to Git"
documentation still referring to mercurial.
The text was updated successfully, but these errors were encountered: