That's not the case, though, "First, the import path is derived in an known way from the URL of the source code. For Bitbucket, GitHub, Google Code, and Launchpad, the root directory of the repository is identified by the repository's main URL, without the http:// prefix."
https://golang.org/doc/articles/go_command.html On Fri, Jul 29, 2016 at 7:10 PM, Michael Jones <michael.jo...@gmail.com> wrote: > Go is strongly opinionated about strategies (reduce errors, simplify > structure, rapid builds, memory safety, etc.) but is agnostic about most > everything else. Even if the Go team uses CPU X, OS Y, VCS Z, that’s just > an example from a multiplicity of present and future choices. The design of > Go needs to span the present and the future—whatever comes after > intel/arm/power, linux/macOS/windows, sccs/rcs/git, vi/emacs/sublime, and > so on in every dimension. It is hard to do at all, much less broadly and > elegantly. > > > > -- > > Michael T. Jones > > > > *From: *<golang-nuts@googlegroups.com> on behalf of Gregory Golberg < > deb...@gmail.com> > *Date: *Friday, July 29, 2016 at 8:54 PM > *To: *golang-nuts <golang-nuts@googlegroups.com> > *Cc: *<deb...@gmail.com> > *Subject: *Re: [go-nuts] Re: What lead to the versionning debate? > > > > But it's already a given that Go is fairly opinionated in favor of github, > no? > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
