From: Jeff King <peff@peff.net>
To: "Reid Woodbury Jr." <reidw@rawsound.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Torsten Bögershausen" <tboegi@web.de>,
git@vger.kernel.org
Subject: Re: git 2.3.4, ssh: Could not resolve hostname
Date: Thu, 2 Apr 2015 15:35:24 -0400 [thread overview]
Message-ID: <20150402193524.GA21555@peff.net> (raw)
In-Reply-To: <62968860-FA58-4339-AF0B-264197EC8A04@rawsound.com>
On Thu, Apr 02, 2015 at 12:31:14PM -0700, Reid Woodbury Jr. wrote:
> Ah, understand. Here's my project URL for 'remote "origin"' with a
> more meaningful representation of their internal FQDN:
>
> url = ssh://rwoodbury@systemname.groupname.online:/opt/git/inventory.git
>
> The "online" is their literal internal TLD.
Thanks. The problem is the extra ":" after "online"; your URL is
malformed. You can just drop that colon entirely.
I do not think we need to support this syntax going forward (the colon
is meaningless here, and our documentation is clear that it should go
with a port number), but on the other hand, it might be nice to be more
liberal, as we were in v2.3.3 and prior. I'll leave it to Torsten to see
whether supporting that would hurt some of the other cases, or whether
it would make the code too awkward.
-Peff
next prev parent reply other threads:[~2015-04-02 19:35 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 [this message]
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=20150402193524.GA21555@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).