BIND 10 #1093: Duplicate message ID should cause program to terminate

[BIND 10 Development]

#1093: Duplicate message ID should cause program to terminate
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:  minor  |            Resolution:
                  Component:         |             Sensitive:  0
  logging                            |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * milestone:   => Next-Sprint-Proposed


Comment:

 Just checked this one out, I'm re-proposing it for next sprint with the
 current changes in the branch (and not the proposed extended checks), the
 changes are minor, and still apply cleanly to master, but they do already
 catch an error currently in a message file (so the only thing left to do
 is to remove the duplicates existing now).

 Further checking of message files would have to wait until we decide on
 whether we want to have strictness or lenience, but this is a small
 improvement we can simply apply now.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1093#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development