sasikanth@gmail.com
*Sent:* Fri Jan 06 01:56:34 PST 2012
*To:* henrik.ho...@millistream.com
*Cc:* bug-wget@gnu.org
*Subject:* Re: [Bug-wget] [PATCH] [wget-bug #32357], IPv6 addresses not
formatted..
Currently we are not checking family type of the address before
printing
the message
--
*From:* Sasikanth sasikanth@gmail.com
*Sent:* Fri Jan 06 01:56:34 PST 2012
*To:* henrik.ho...@millistream.com
*Cc:* bug-wget@gnu.org
*Subject:* Re: [Bug-wget] [PATCH] [wget-bug #32357], IPv6
addresses not
formatted
Micah Cowan mi...@micah.cowan.name writes:
I believe hh's suggestion is to have the format reflect the way it would look
in a URL; so [ and ] around ipv6, and nothing around ipv4 (since ipv4 format
isn't ambiguous in the way ipv6 is).
I agree. Please rework your patch to use
#32357], IPv6 addresses not
formatted..
Currently we are not checking family type of the address before printing
the message.
Do we have to print the message as [3ffe:b80:17e2::1]:80 for ipv6 and
|10.0.0.1|:80 for ipv4?
Please confirm so I will resubmit patch.
Thanks
Sasi
Note: I didn't
)
-mjc
Sent from my Kindle Fire
--
*From:* Sasikanth sasikanth@gmail.com
*Sent:* Fri Jan 06 01:56:34 PST 2012
*To:* henrik.ho...@millistream.com
*Cc:* bug-wget@gnu.org
*Subject:* Re: [Bug-wget] [PATCH] [wget-bug #32357], IPv6 addresses not
formatted
Currently we are not checking family type of the address before printing
the message.
Do we have to print the message as [3ffe:b80:17e2::1]:80 for ipv6 and
|10.0.0.1|:80 for ipv4?
Please confirm so I will resubmit patch.
Thanks
Sasi
Note: I didn't get the reply to my mail, to keep track the
_
From: Sasikanth sasikanth@gmail.com
Sent: Fri Jan 06 01:56:34 PST 2012
To: henrik.ho...@millistream.com
Cc: bug-wget@gnu.org
Subject: Re: [Bug-wget] [PATCH] [wget-bug #32357], IPv6 addresses not
formatted..
Currently we are not checking family type of the address before printing
