From: Junio C Hamano <gitster@pobox.com>
To: "Reid Woodbury Jr." <reidw@rawsound.com>
Cc: "Jeff King" <peff@peff.net>,
"Torsten Bögershausen" <tboegi@web.de>,
git@vger.kernel.org
Subject: Re: git 2.3.4, ssh: Could not resolve hostname
Date: Thu, 02 Apr 2015 12:24:38 -0700 [thread overview]
Message-ID: <xmqq7ftujpu1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150402191452.GA20420@peff.net> (Jeff King's message of "Thu, 2 Apr 2015 15:14:52 -0400")
Jeff King <peff@peff.net> writes:
> but this does not:
>
> $ git push ssh://does-not-exist:/repo.git
> ssh: Could not resolve hostname does-not-exist:: No address associated with hostname
>
> (note the doubled colon). v2.3.3 did strip off that extra colon, but I
> am not sure the URL above (i.e., a colon with no hostname) is actually
> sane. IOW, it may have happened to work in older versions, but I'm not
> sure we would want to promise to keep it working.
>
> Can you show us what your URL looks like, obfuscating the names but
> keeping the syntax the same? Also, are you using the "insteadOf" config
> syntax at all (which could easily lead to funny splicing, I imagine).
Everything Jeff said ;-)
Depending on the nature of 'xxxx' in the original, Torsten's
response may be different. 'xxxx' could stand for [9999:9999::9999],
a.host.in.domain.xz, 127.0.0.1, or all the other things and it is a
bit too vague to help us tell which codepath will pick up what and
possibly screw it up.
next prev parent reply other threads:[~2015-04-02 19:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 17:18 git 2.3.4, ssh: Could not resolve hostname Reid Woodbury Jr.
2015-04-02 18:09 ` Jeff King
2015-04-02 18:58 ` Reid Woodbury Jr.
2015-04-02 19:14 ` Jeff King
2015-04-02 19:24 ` Junio C Hamano [this message]
2015-04-02 19:31 ` Reid Woodbury Jr.
2015-04-02 19:35 ` Jeff King
2015-04-02 20:06 ` Reid Woodbury Jr.
2015-04-02 20:15 ` Thomas Schneider
2015-04-03 0:02 ` Torsten Bögershausen
2015-04-03 1:30 ` brian m. carlson
2015-04-03 21:01 ` Junio C Hamano
2015-04-03 21:05 ` Jeff King
2015-04-03 21:32 ` Kyle J. McKay
2015-04-04 0:19 ` Reid Woodbury Jr.
2015-04-04 7:21 ` Torsten Bögershausen
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=xmqq7ftujpu1.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=reidw@rawsound.com \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.