-
Notifications
You must be signed in to change notification settings - Fork 18k
all: spelling inconsistency for networking terms #17613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Where is |
s/7791/7719/g |
I would instead encourage us to avoid the term "hostname" unless it specifically refers to the operating system's notion of hostname. (As RFC 7719 mentions, the hostname often does not include the domain part.) |
@mdempsky tackled this issue a bit for Lookup functions and used the term |
CL https://golang.org/cl/34875 mentions this issue. |
CL https://golang.org/cl/34876 mentions this issue. |
CL https://golang.org/cl/34879 mentions this issue. |
This change clarifies the documentation on Dial and its variants to avoid unnecessary confusion about how the arguments for the connection setup functions are used to make connections. Also replaces "name" or "hostname" with "host name" when the term implies the use of DNS. Updates #17613. Fixes #17614. Fixes #17738. Fixes #17956. Updates #18806. Change-Id: I6adb3f2ae04a3bf83b96016ed73d8e59926f3e8a Reviewed-on: https://go-review.googlesource.com/34875 Reviewed-by: Ian Lance Taylor <[email protected]>
This change clarifies the documentation on Listen and ListenPacket to avoid unnecessary confusion about how the arguments for the connection setup functions are used to make connections. Also replaces "name" or "hostname" with "host name" when the term implies the use of DNS. Updates #17613. Updates #17614. Updates #17615. Fixes #17616. Updates #17738. Updates #17956. Change-Id: I0bad2e143207666f2358d397fc076548ee6c3ae9 Reviewed-on: https://go-review.googlesource.com/34876 Reviewed-by: Ian Lance Taylor <[email protected]>
This change clarifies the documentation on Resolve{TCP,UDP,IP,Unix}Addr to avoid unnecessary confusion about how the arguments are used to make end point addresses. Also replaces "name" or "hostname" with "host name" when the term implies the use of DNS. Updates #17613. Change-Id: Id6be87fe2e4666eecd5b92f18ad8b9a6c50a2bd6 Reviewed-on: https://go-review.googlesource.com/34879 Reviewed-by: Ian Lance Taylor <[email protected]>
CL https://golang.org/cl/49750 mentions this issue. |
Updates golang/go#17613 Change-Id: I0b272c19c263f20084a936b5122bb3cfebacc752 Reviewed-on: https://go-review.googlesource.com/49750 Reviewed-by: Brad Fitzpatrick <[email protected]>
This looks like it was all done, the remaining references to |
Some packages use
hostname
and othershost name
. The worst is the net package which uses both. It might be better to align tohost name
defined in https://tools.ietf.org/html/rfc7719.The text was updated successfully, but these errors were encountered: