BIND 10 trac2571_commit_log_fix, updated. f65147ed98354cb39e52568a6ff1f7f98ad885ff [2571] Explain unit test for character 255.

[BIND 10 source code commits]

The branch, trac2571_commit_log_fix has been updated
  discards  5e1b58d8df60d78e58a883832aea8dd5a9282c82 (commit)
  discards  b88bb61f7547158719b8329c8ddf7b8e36ef2185 (commit)
  discards  ebafb410bb11302041292acc587555926de258f1 (commit)
  discards  9e6c81fa228570d6476d1cd7b8ead3a9e89e9301 (commit)
       via  f65147ed98354cb39e52568a6ff1f7f98ad885ff (commit)
       via  1c59e1ee00a8d1ebabfabb592ee910b22c72f1d9 (commit)
       via  63c3bee3545216695dacb5b06c52c90ab82f31ec (commit)
       via  6b6cbde6a1ac6ad0f3f11923ee6633ced00d529b (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (5e1b58d8df60d78e58a883832aea8dd5a9282c82)
            \
             N -- N -- N (f65147ed98354cb39e52568a6ff1f7f98ad885ff)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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 f65147ed98354cb39e52568a6ff1f7f98ad885ff
Author: Shane Kerr <shane at isc.org>
Date:   Mon Jan 14 16:51:21 2013 +0100

    [2571] Explain unit test for character 255.

commit 1c59e1ee00a8d1ebabfabb592ee910b22c72f1d9
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Tue Jan 8 20:18:06 2013 -0800

    [2571] a small optimization: avoid calling strlen() every time in loop

commit 63c3bee3545216695dacb5b06c52c90ab82f31ec
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Tue Jan 8 20:12:37 2013 -0800

    [2571] editorial cleanups: &/* position, use camel name for func; const

commit 6b6cbde6a1ac6ad0f3f11923ee6633ced00d529b
Author: Shane Kerr <shane at isc.org>
Date:   Fri Dec 21 10:11:05 2012 +0100

    [2571] Change from char to int when we need special character values.
    
    In cases where we use values outside of normal character range (-128
    to 127 or 0 to 255) to indicate special things, like EOF, we need to
    insure that we can hold these values. To do that, we use an int.
    
    It turns out that the default type conversions also meant that our
    JSON conversion from strings would break in some cases. A test was
    added to show that, and to confirm the fix.

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

Summary of changes:

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