Comment 1:

hi beatgammit, do you want to contribute that patch?
please read http://golang.org/doc/contribute.html if do.
or we can take care the 1-line patch for you if you don't bother to set up the
mercurial plugin (that is, you don't expect to contribute other patches in the
near future).
i think this is trivial and simple enough to fix for Go 1.1.

Labels changed: added priority-soon, go1.1, removed priority-triage.

Status changed to Accepted.

Comment 2 by beatgammit:

Let's go ahead and do the code review: https://golang.org/cl/9210043/
I plan to submit patches after 1.1 is released, so this will be a nice simple intro to
contributing.

Comment 3:

ok. just "hg mail 9210043" after Go 1.1 is released.

Labels changed: added priority-later, removed priority-soon, go1.1.

Comment 4:

Labels changed: added go1.2maybe.

Status changed to Started.

Comment 5:

Labels changed: added feature.

Comment 6:

Issue #6030 has been merged into this issue.

Comment 7:

This issue was closed by revision 65f21ca.

Status changed to Fixed.

Comment 8:

FWIW, reverting this CL. I tried to create such a clone earlier today and found that I
cannot. On further inquiry I've been told that that feature has been turned off. I don't
see a strong argument for making such imports work starting in Go 1.2 when you cannot
create new ones. (It does appear that old ones are still available, but given that they
won't work with Go pre-1.2 the benefit seems marginal at best.)

Comment 9:

This issue was updated by revision 913f1f1.

R=golang-dev, dave, r
CC=golang-dev
https://golang.org/cl/13317046

Comment 10 by wkharold:

To date this feature has NOT been turned off. I just created a clone of a
code.google.com repo - specifically go9p. It wound up being
code.google.com/r/<mumble>-go9p. Attempting to go get the cloned repo yields the
dreaded invalid code.google.com/ import path error. The obvious workaround is to create
a local copy, strip the VCS info out of it, and load it into github or bitbucket. This
makes contributing fixes/enhancements upstream tedious and error
prone. Please reconsider making the go tool chain recognize code.google.com/r paths.

Comment 11:

Cloning a code.google.com repo was turned off and then turned on again.  Reopening this
issue.  Unless cloning is turned off again.

Labels changed: added repo-main, release-go1.4, removed priority-later, go1.2maybe, feature.

Status changed to Accepted.

Comment 12:

I don't think this is important enough.

Status changed to WorkingAsIntended.

Comment 13 by majid@apsalar.com:

I just cloned a /p/ repo and got a /r/ URL. It seems you can replace /r/ with /p/ and
Google Code will redirect, so there is a work-around, but it's a simple change that
would make for better usability.
Case in point:
Fails: go get code.google.com/r/majid-leveldb-go/leveldb
Works: go get code.google.com/p/majid-leveldb-go/leveldb