From afa1c6a2dfef06e56b2410c7ab430b0a36d2b69f Mon Sep 17 00:00:00 2001 From: nobu Date: Sun, 11 Nov 2018 00:46:31 +0000 Subject: [PATCH] Use friendlier terminology in rubysocket.h comment [Fix GH-2008] From: Juanito Fatas git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65662 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- ext/socket/rubysocket.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ext/socket/rubysocket.h b/ext/socket/rubysocket.h index 922df9b87b..88143bfe0e 100644 --- a/ext/socket/rubysocket.h +++ b/ext/socket/rubysocket.h @@ -408,7 +408,7 @@ NORETURN(void rsock_sys_fail_raddrinfo_or_sockaddr(const char *, VALUE addr, VAL * all cases. For some syscalls (e.g. accept/accept4), blocking on the * syscall instead of relying on select/poll allows the kernel to use * "wake-one" behavior and avoid the thundering herd problem. - * This is likely safe on all other *nix-like systems, so this whitelist + * This is likely safe on all other *nix-like systems, so this safe list * can be expanded by interested parties. */ #if defined(__linux__)