Correct bug in timeout receive

It was possible for the timeout receive function to return a
nil message buffer pointer, even if the calling function passed
a pointer in for reuse.  The exposure was limited only to when
the epoll environment could not be initialised which we believe
has never been observed.

Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I259a5e5a0a18e53ffb03cc4c47d171e77e998835
diff --git a/CHANGES b/CHANGES
index 6271785..aead0f9 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,14 @@
-pic2
-API and build change  and fixe summaries. Doc correctsions
+
+API and build change  and fix summaries. Doc correctsions
 and/or changes are not mentioned here; see the commit messages.
 
+2019 October 21; version 1.10.1
+	Fix to prevent null message buffer from being returned by the timeout
+	receive function if the function is passed one to reuse.
+
+2019 October 21; version 1.10.1
+	Add periodic dump of send count info to stderr.
+
 2019 September 27; version 1.9.0
 	Python bindings added receive all queued function and corrected a unit test