BIND 10 trac764, updated. 65bc0fbf12199bee2d16b914a544a69345c37cae [trac764] editorial suggestions: s/packet/message/

[BIND 10 source code commits]

The branch, trac764 has been updated
       via  65bc0fbf12199bee2d16b914a544a69345c37cae (commit)
      from  9ff2f7bc88be85c09d37209bd0feeb96ca256892 (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 65bc0fbf12199bee2d16b914a544a69345c37cae
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Mon Jul 11 02:17:44 2011 -0700

    [trac764] editorial suggestions: s/packet/message/

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

Summary of changes:
 src/lib/python/isc/notify/notify_out_messages.mes |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/python/isc/notify/notify_out_messages.mes b/src/lib/python/isc/notify/notify_out_messages.mes
index 797643e..f77446a 100644
--- a/src/lib/python/isc/notify/notify_out_messages.mes
+++ b/src/lib/python/isc/notify/notify_out_messages.mes
@@ -23,7 +23,7 @@ is not correct. The specific place where this library needs to be
 depends on your system and your specific installation.
 
 % NOTIFY_OUT_INVALID_ADDRESS invalid address %1#%2: %3
-The notify_out library tried to send a notify packet to the given
+The notify_out library tried to send a notify message to the given
 address, but it appears to be an invalid address. The configuration
 for secondary nameservers might contain a typographic error, or a
 different BIND 10 module has forgotten to validate its data before
@@ -50,7 +50,7 @@ the one we sent. Since there was a response, no more notifies will
 be sent to this server for this notification event.
 
 % NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1#%2
-The notify_out library sent a notify packet to the namesever at the
+The notify_out library sent a notify message to the namesever at the
 given address, but the reply did not have the QR bit set to one.
 
 % NOTIFY_OUT_RETRY_EXCEEDED notify to %1#%2: number of retries (%3) exceeded
@@ -63,13 +63,13 @@ A notify message is sent to the secondary nameserver at the given
 address.
 
 % NOTIFY_OUT_SOCKET_ERROR socket error sending notify to %1#%2: %3
-There was a network error while trying to send a notify packet to
+There was a network error while trying to send a notify message to
 the given address. The address might be unreachable. The socket
 error is printed and should provide more information.
 
 % NOTIFY_OUT_SOCKET_RECV_ERROR socket error reading notify reply from %1#%2: %3
 There was a network error while trying to read a notify reply
-packet from the given address. The socket error is printed and should
+message from the given address. The socket error is printed and should
 provide more information.
 
 % NOTIFY_OUT_TIMEOUT retry notify to %1#%2
@@ -79,8 +79,8 @@ is reached.
 
 % NOTIFY_OUT_REPLY_UNCAUGHT_EXCEPTION uncaught exception: %1
 There was an uncaught exception in the handling of a notify reply
-packet, either in the packet parser, or while trying to extract data
-from the parsed packet. The error is printed, and notify_out will
-treat the response as a bad packet, but this does point to a
+message, either in the message parser, or while trying to extract data
+from the parsed message. The error is printed, and notify_out will
+treat the response as a bad message, but this does point to a
 programming error, since all exceptions should have been caught
 explicitely. Please file a bug report.