BIND 10 trac2091a, updated. 626757dd1e83316204873790197a3f151fd91696 [2091a] more clarification on the use of separate memsgmt for each zone.

[BIND 10 source code commits]

The branch, trac2091a has been updated
       via  626757dd1e83316204873790197a3f151fd91696 (commit)
      from  6535fcf60c69445751261e593a1f740e77fbd0bb (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 626757dd1e83316204873790197a3f151fd91696
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Tue Jul 24 10:26:05 2012 -0700

    [2091a] more clarification on the use of separate memsgmt for each zone.
    
    also fixed some text that didn't really make sense.

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

Summary of changes:
 src/lib/datasrc/memory_datasrc.cc |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/datasrc/memory_datasrc.cc b/src/lib/datasrc/memory_datasrc.cc
index 652b3b1..d11834d 100644
--- a/src/lib/datasrc/memory_datasrc.cc
+++ b/src/lib/datasrc/memory_datasrc.cc
@@ -147,9 +147,11 @@ struct ZoneData {
 
         // The assert may be too harsh, but we assume we'll discard (rewrite)
         // this code soon enough.  Until then this would be a good way to
-        // detect any memory leak.  Also, at that point we shouldn't use
-        // a single separate memory segment for each zone tree; normally
-        // zone data for multiple zones will be managed in a single segment.
+        // detect any memory leak.  Also, at that point we should use
+        // a single separate memory segment for each zone tree; eventually
+        // zone data for multiple zones will be managed in a single segment,
+        // at which point the segment will be passed from outside of this
+        // module.
         assert(local_mem_sgmt_.allMemoryDeallocated());
     }