On Tue, 27 Sep 2016, David Drysdale via c-ares wrote:
>> That made me think. Do you think we should bump the version number for the
>> pending release to 1.12.0 because of this new ARES_OPT_NOROTATE value?
> That probably makes sense -- I think the change is generally
> back-compatible, but there is a slight API extension (in that a new bit can
> now show up in the optmask).
Then let's do that.
Oh and btw, I think you forgot to add a ARES_OPT_NOROTATE description to
ares_init_options.3 (we actually lack docs for several other OPTs too).
-- / daniel.haxx.seReceived on 2016-09-29