On Tue, 13 Sep 2011 04:04:04 -0700 (PDT)
tombert <tomb...@live.at> wrote:

> >  * According to the "GIT URLS" section of the git-clone manual page,
> >    a stray colon between the server and path components is only
> > allowed when working over SSH (to mimic scp's convention).
> >    So are you cloning via SSH?  I would not be surprised it doesn't
> > work for git:// or http[s]://.
> >  * Shouldn't this problem be reported to the TortoiseGit's tracker?
> >    Personally, I don't care but I think it's a good idea.
> sorry for the missing context: yes it's windows xp.
> Yes it is ssh, and I even can write:
> git clone ssh://tom@myserver:/cmdata/git/myproject
> which gives an error, but ommiting the colon sucessfully resolves the
> hostname.
> This is not a TortoiseGit bug - so why report?
That wasn't easily understandable (at least for me).

Well, I just did some testing -- the idea is that "server:path" is only
viable without the "ssh://" schema prefix (because it implies SSH
itself).  Hence `git clone user@server:path` works OK for me both with
Git (Debian Linux) and 1.7.6.msysgit.0.
This is obviously not a bug because Git behaves exactly as stated in its
`git-clone` manual page; we just read it too creatively.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to