Yeah, I'm ok with this.
go for it
On Thu, Jun 30, 2016 at 6:59 AM, Brent Cook wrote:
> As a precedent, nc has a conversational, specific style of error
> reporting when a socketopt fails. With the IPv4/6-specific options, we
> refactored the code to the point that the error messages are less
>
As a precedent, nc has a conversational, specific style of error
reporting when a socketopt fails. With the IPv4/6-specific options, we
refactored the code to the point that the error messages are less
specific and maybe misleading (e.g. setting ToS on an IPv6 socket).
This patch makes the per-add