25 Oct
2013
25 Oct
'13
1:59 p.m.
On Fri, Oct 25, 2013 at 01:14:41PM +0200, Philip Homburg <philip.homburg@ripe.net> wrote a message of 25 lines which said:
One obvious bug is that this behavior is not documented.
It is much worse: it _is_ documented and the documentation is wrong. I spent two hours on that this morning and, as you can imagine, I'm not happy.
Another thing is that just silently setting the flag is not optimal,
It is not "not optimal", it is _wrong_.
maybe the measurement should have been rejected instead.
And the documentation fixed!