Greetings, 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). Mahmoud Al-Qudsi NeoSmart Technologies
