BIND 10 master, updated. aafb86a4203109142c6f888a2548fe57dd0dd701 [master] changelog for #2934

[BIND 10 source code commits]

The branch, master has been updated
       via  aafb86a4203109142c6f888a2548fe57dd0dd701 (commit)
      from  bde0e94518469557c8b455ccbecc079a38382afd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit aafb86a4203109142c6f888a2548fe57dd0dd701
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Thu May 23 16:07:21 2013 -0700

    [master] changelog for #2934

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog |   23 +++++++++++++++--------
 1 file changed, 15 insertions(+), 8 deletions(-)

-----------------------------------------------------------------------
diff --git a/ChangeLog b/ChangeLog
index 8f31541..e092a24 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,12 +1,19 @@
+615.	[bug]		jinmei
+	b10-xfrout now uses blocking send for xfr response messages
+	to prevent abrupt termination of the stream due to a slower
+	client or narrower network bandwidth.
+	(Trac #2934, git bde0e94518469557c8b455ccbecc079a38382afd)
+
 618.	[func]*		marcin
-	b10-dhcp4: Added the ability for the server to respond to a directly
-        connected client which does not yet have an IP address.  On Linux, the
-        server will unicast the	response to the client's hardware address and
-        the 'yiaddr' (the client's new IP address). Sending a response to the
-        unicast address prevents other (not interested) hosts from receiving
-        the server response. This capability is not yet implemented on non-Linux
-        Operating Systems where, in all cases, the server responds to the
-        broadcast address. The logic conforms to section 4.1 of RFC 2131.
+	b10-dhcp4: Added the ability for the server to respond to a
+	directly connected client which does not yet have an IP address.
+	On Linux, the server will unicast the response to the client's
+	hardware address and the 'yiaddr' (the client's new IP
+	address). Sending a response to the unicast address prevents other
+	(not interested) hosts from receiving the server response. This
+	capability is not yet implemented on non-Linux Operating Systems
+	where, in all cases, the server responds to the broadcast
+	address. The logic conforms to section 4.1 of RFC 2131.
 	(Trac #2902, git c2d40e3d425f1e51647be6a717c4a97d7ca3c29c)
 
 617.	[bug]		marcin