What actually happens when you use the ssh:// style connection?
Be it ssh://host/full/path or host:/full/path or host:path/in/home, you
log in as whatver ssh identifies you as to the server, and start a
server-side git process over there.
Ah ok, that makes more sense. Strange then if it's a server-side git
process that it ignores the server's /etc/gitconfig where aliases can be
set up.
With ssh://host/path notation, there is no way to specify any relative
path (i.e. "/path" part begins at root) so it will mean the same thing for
everybody (unless you are getting chrooted or something), while host:path
notation allows relative path which will be taken relative as where you
are, i.e. home directory of the user on the server.
In that case I symlinked my repository folder to /git so that SSH users
can "cd /git/project.git" and this seems to work well. I can now use
git URLs like ssh://server/git/project.git even though the repos are
buried much deeper down in the tree.
Thanks for the explanations!
Cheers,
Adam.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html