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, while `git clone ssh://g...@example.com:2222/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:2222/path` (I'm not >sure what it will do with the `:2222` should the connection actually succeed). Git is attempting to resolve the repository "2222/path" as it's default behaviour since the ssh method is not specified. This is a situation where the default is ambiguous so while git is choosing the ssh method, it is also choosing repository resolution after the ':' which is also default behaviour. Cheers, Randall -- Brief whoami: NonStop&UNIX developer since approximately UNIX(421664400)/NonStop(211288444200000000) -- In my real life, I talk too much.
