From: Junio C Hamano <junkio@cox.net>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] GIT: Support [address] in URLs
Date: Wed, 21 Dec 2005 14:16:50 -0800 [thread overview]
Message-ID: <7v64pi5c4t.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051221.192342.132228413.yoshfuji@linux-ipv6.org> (YOSHIFUJI Hideaki's message of "Wed, 21 Dec 2005 19:23:42 +0900 (JST)")
[somehow the first reply seems to have been lost]
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org> writes:
> Allow address enclosed by [] in URLs, like:
> git push '[3ffe:ffff:...:1]:GIT/git'
> or
> git push 'ssh://[3ffe:ffff:...:1]/GIT/git'
I am not familiar with how things are done in ipv6 land, but I
wonder if the former is consistent with the existing practice.
That is, how does one do something like this, with an ipv6
literal address?
telnet 127.0.0.1 80
Is it done like this
telnet '[::1]' 80
or
telnet '::1' 80
Your patch suggests the former, but I just wanted to make sure.
The latter "ssh://[...]" looks like RFC 3986, and I do not have
problems with.
next prev parent reply other threads:[~2005-12-21 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 10:23 [PATCH] GIT: Support [address] in URLs YOSHIFUJI Hideaki / 吉藤英明
2005-12-21 22:16 ` Junio C Hamano [this message]
[not found] ` <7vr7866uww.fsf@assigned-by-dhcp.cox.net>
2005-12-21 22:20 ` YOSHIFUJI Hideaki / 吉藤英明
[not found] ` <7v1x065blx.fsf@assigned-by-dhcp.cox.net>
2005-12-21 23:03 ` Junio C Hamano
[not found] ` <7v3bkm3vw4.fsf@assigned-by-dhcp.cox.net>
2005-12-21 23:08 ` YOSHIFUJI Hideaki / 吉藤英明
2005-12-21 23:24 ` [OT] western cultural imperialism at vger? Junio C Hamano
2005-12-21 23:29 ` David S. Miller
2005-12-21 23:38 ` Krzysztof Halasa
2005-12-21 23:46 ` David S. Miller
2005-12-21 23:26 ` [PATCH] GIT: Support [address] in URLs David S. Miller
2005-12-21 23:59 ` YOSHIFUJI Hideaki / 吉藤英明
2005-12-22 0:08 ` David S. Miller
2005-12-22 16:48 ` Daniel Barkalow
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=7v64pi5c4t.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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.