On December 10, 2017 3:24 PM Mahmoud wrote:
>It appears that for non-standard ports to be specified for ssh-based
clones/checkouts, the leading "ssh://" prefix must
>be applied. I am unsure if there's a reason for this or if it is simply an
overlooked idiosyncrasy in the parser.
>Basically,
"mqu...@neosmart.net" writes:
> Basically, while `git clone ssh://g...@example.com:/path` works, the same
> with the `ssh://` prefix doesn't, and attempts to establish a connection to
> port 22 instead: `git clone g...@example.com:/path` (I'm not sure what it
> will
2 matches
Mail list logo