Git doesn't care if the / is there or not ([email protected]:user/foo.git and [email protected]:/user/foo.git behave identically)
the go tool expects the slash to be there when it converts from scp-like paths to https: $ go get [email protected]:user/foo.git package [email protected]:user/foo.git: unrecognized import path "[email protected]:user/foo.git" (https fetch: Get https://[email protected]:user/foo.git?go-get=1: invalid URL port "user") On Tue, Mar 21, 2017 at 9:52 AM, Jan Mercl <[email protected]> wrote: > > On Tue, Mar 21, 2017 at 4:44 PM andrey mirtchovski <[email protected]> > wrote: > >> any suggestions? > > AFAICT, public as well as private Github repository URLs do _not_ have the > slash after the colon in the URL, like in [email protected]:user/foo.git. > > -- > > -j -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
