From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Reid Woodbury Jr." <reidw@rawsound.com>,
git@vger.kernel.org
Subject: Re: git 2.3.4, ssh: Could not resolve hostname
Date: Fri, 3 Apr 2015 17:05:47 -0400 [thread overview]
Message-ID: <20150403210547.GA10380@peff.net> (raw)
In-Reply-To: <xmqqy4m9exj0.fsf@gitster.dls.corp.google.com>
On Fri, Apr 03, 2015 at 02:01:55PM -0700, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
> > This makes my think that it is
> > a) non-standard to have the extra colon
> > b) The error message could be better
>
> For that, perhaps
>
> -ssh: Could not resolve hostname xxxx:: nodename nor servname provided, or not known
> +ssh: Could not resolve hostname "xxxx:": nodename nor servname provided, or not known
>
> would be something we would want to do, no matter what other fixes
> we would apply.
That message comes from the ssh client. So the "we" here would have to submit a
patch to OpenSSH".
The easier way to diagnose inside git is to set GIT_TRACE, which makes
it more clear:
$ GIT_TRACE=1 git clone ssh://bogosity:/repo.git
...
17:05:00.734019 run-command.c:347 trace: run_command: 'ssh' 'bogosity:' 'git-upload-pack '\''/repo.git'\'''
-Peff
next prev parent reply other threads:[~2015-04-03 21:05 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
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 [this message]
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=20150403210547.GA10380@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).