Jason Tedor 9a0fd3a7b8 Do not log on explicit no unsafe again ... Motivation: Users should not see a scary log message when Netty is initialized if Netty configuration explicitly disables unsafe. The log message that produces this warning was previously guarded but the guard was lost. Modifications: This commit brings back the guard against the scary log message if unsafe is explicitly disabled. Result: No log message is produced when unsafe is unavailable because Netty was told to not look for it.		2017-05-03 13:29:58 -07:00
..
main	Do not log on explicit no unsafe again	2017-05-03 13:29:58 -07:00
test	Introduce HashedWheelTimer.pendingTimeouts()	2017-05-01 20:10:22 -07:00