Am 27.09.2013 10:07, schrieb Morten Stenshorne:
> I've just upgraded to Debian testing (jessie), and with that I got a
> brand new (for me) git version:
>
> $ git --version
> git version 1.8.4.rc3
>
> Some of my repos I use an ssh tunnel to reach, so when I want to reach a
> repo forwarded to local port 2223, using the ssh protocol, the following
> used to work (.git/config) in older git versions:
>
> [remote "exp"]
> url = [localhost:2223]:blink.git
> fetch = +refs/heads/*:refs/remotes/exp/*
>
> However, now I get this message:
>
> $ git fetch exp
> fatal: ':blink.git' does not appear to be a git repository
> fatal: Could not read from remote repository.
I wonder why that worked (especially the "[...]") at all ?
I thought specifying a port for a SSH connection was always only
possible when using
ssh://user@host:port/path/to/repo.git
- or -
ssh://user@host:port/~user/path/to/repo.git
At least that's what I always read out of the git-clone man page.
Stefan
--
----------------------------------------------------------------
/dev/random says: Don't ask me, I have random access memory.
python -c "print
'73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
