git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Morten Stenshorne <mstensho@opera.com>
To: git@vger.kernel.org
Subject: Bug: [hostname:port]:repo.git notation no longer works (for ssh)
Date: Fri, 27 Sep 2013 10:07:26 +0200	[thread overview]
Message-ID: <87vc1mg01t.fsf@aeneas.oslo.osa> (raw)

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.

    Please make sure you have the correct access rights
    and the repository exists.

If I don't go via the ssh tunnel (I finally have some VPN stuff these
days, so I don't really need the tunnel thing anymore, but that's going
to be a lot of remotes to update, so I'd prefer it just worked like it
used to):

-            url = [localhost:2223]:blink.git
+            url = git:blink.git

... it works fine.

-- 
---- Morten Stenshorne, developer, Opera Software ASA ----
------------------ http://www.opera.com/ -----------------

             reply	other threads:[~2013-09-27  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  8:07 Morten Stenshorne [this message]
2013-09-27  8:38 ` Bug: [hostname:port]:repo.git notation no longer works (for ssh) Duy Nguyen
2013-09-27  8:55 ` Stefan Näwe
2013-09-27 13:48   ` Duy Nguyen
2013-09-27 14:31 ` Phil Hord
2013-09-27 14:43   ` Morten Stenshorne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vc1mg01t.fsf@aeneas.oslo.osa \
    --to=mstensho@opera.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).