git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
Cc: Morten Stenshorne <mstensho@opera.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Bug: [hostname:port]:repo.git notation no longer works (for ssh)
Date: Fri, 27 Sep 2013 20:48:18 +0700	[thread overview]
Message-ID: <CACsJy8CURVVpdGGJgpG2abJ3yo+fEnbeXS1Dug4zPCJ=zMLxmQ@mail.gmail.com> (raw)
In-Reply-To: <524547E8.4070406@atlas-elektronik.com>

On Fri, Sep 27, 2013 at 3:55 PM, Stefan Näwe
<stefan.naewe@atlas-elektronik.com> wrote:
>>     [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.

[] is used to wrap ipv6 and because we don't know if it's actually
ipv6 or v4, we accept it in both cases, so [abc] can be used in place
"host" above. No [host:port]:path won't work because "host:port" is
considered host name. But [host or ip]:path may work (that is after I
fix my bug).
-- 
Duy

  reply	other threads:[~2013-09-27 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  8:07 Bug: [hostname:port]:repo.git notation no longer works (for ssh) Morten Stenshorne
2013-09-27  8:38 ` Duy Nguyen
2013-09-27  8:55 ` Stefan Näwe
2013-09-27 13:48   ` Duy Nguyen [this message]
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='CACsJy8CURVVpdGGJgpG2abJ3yo+fEnbeXS1Dug4zPCJ=zMLxmQ@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mstensho@opera.com \
    --cc=stefan.naewe@atlas-elektronik.com \
    /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).