git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: junkio@cox.net
Cc: git@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] GIT: Support [address] in URLs
Date: Thu, 22 Dec 2005 07:20:45 +0900 (JST)	[thread overview]
Message-ID: <20051222.072045.31468866.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <7vr7866uww.fsf@assigned-by-dhcp.cox.net>

In article <7vr7866uww.fsf@assigned-by-dhcp.cox.net> (at Wed, 21 Dec 2005 12:45:51 -0800), Junio C Hamano <junkio@cox.net> says:

> 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.

In this case (telnet), we do the latter.
But, we definitely do
        scp file1 file2 ... '[3ffe:ffff:...:1]:/tmp/'
like
        scp file1 file2 ... remote.example.com:/tmp/

Hope this helps.

--yoshfuji

  parent reply	other threads:[~2005-12-21 22:20 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
     [not found] ` <7vr7866uww.fsf@assigned-by-dhcp.cox.net>
2005-12-21 22:20   ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
     [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=20051222.072045.31468866.yoshfuji@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).