More --debug options, split code into separate objects.

1 files changed, 8 insertions, 9 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index b88b2ebc..47976b33 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -5,11 +5,10 @@ Change history for Coverage.py
 3.6.1
 -----
 
-- Added the ``--debug`` switch to ``coverage run``.  It accepts one option now,
-  ``trace``, to log decisions whether to trace files.  I'm hoping this will
-  help people diagnose why their code isn't being traced.
+- Added the ``--debug`` switch to ``coverage run``.  It accepts a list of
+  options indicating the type of internal activity to log to stderr.
 
-- Improved the branch coverage facility, fixing `issue 90`_ and `issue 175`_.
+- Improved the branch coverage facility, fixing `issue 92`_ and `issue 175`_.
 
 - Running code with ``coverage run -m`` now behaves more like Python does,
   setting sys.path properly, which fixes `issue 207`_ and `issue 242`_.
@@ -18,12 +17,12 @@ Change history for Coverage.py
   cause them to be incorrectly marked as unexecuted, as described in
   `issue 218`_.  This is now fixed.
 
-- When running a threaded program under the Python tracer, coverage would issue
-  a spurious warning about the trace function changing: "Trace function
-  changed, measurement is likely wrong: None." This fixes `issue 164`_.
+- When running a threaded program under the Python tracer, coverage no longer
+  issues a spurious warning about the trace function changing: "Trace function
+  changed, measurement is likely wrong: None."  This fixes `issue 164`_.
 
-- The source kit omitted the __main__.py file in the root coverage directory.
-  It's now included, fixing `issue 255`_.
+- The source kit now includes the `__main__.py` file in the root coverage
+  directory, fixing `issue 255`_.
 
 .. _issue 92: https://bitbucket.org/ned/coveragepy/issue/92/finally-clauses-arent-treated-properly-in
 .. _issue 164: https://bitbucket.org/ned/coveragepy/issue/164/trace-function-changed-warning-when-using