Update the history timestamps.

8 files changed, 20 insertions, 0 deletions

diff --git a/doc/api.rst b/doc/api.rst
index fe4c3ac5..09b94af4 100644
--- a/doc/api.rst
+++ b/doc/api.rst
@@ -7,6 +7,8 @@ Coverage API
 :history: 20090524T134300, brand new docs.
 :history: 20090613T164000, final touches for 3.0
 :history: 20100221T151500, docs for 3.3 (on the plane back from PyCon)
+:history: 20100725T211700, updated for 3.4.
+
 
 The API to coverage.py is very simple, contained in a single module called
 `coverage`.  Most of the interface is in a single class, also called
diff --git a/doc/branch.rst b/doc/branch.rst
index 8f1583a1..2607bfdb 100644
--- a/doc/branch.rst
+++ b/doc/branch.rst
@@ -5,6 +5,7 @@ Branch coverage measurement
 ===========================
 
 :history: 20091127T201300, new for version 3.2
+:history: 20100725T211700, updated for 3.4.
 
 .. highlight:: python
    :linenothreshold: 5
diff --git a/doc/changes.rst b/doc/changes.rst
index 8c3285c6..c6d8d15d 100644
--- a/doc/changes.rst
+++ b/doc/changes.rst
@@ -12,6 +12,8 @@ Major change history for coverage.py
 :history: 20091205T161525, 3.2 final
 :history: 20100221T151900, changes for 3.3
 :history: 20100306T181400, changes for 3.3.1
+:history: 20100725T211700, updated for 3.4.
+
 
 These are the major changes for coverage.py.  For a more complete change
 history, see the `CHANGES.txt`_ file in the source tree.
diff --git a/doc/cmd.rst b/doc/cmd.rst
index b31b3d1d..053ed139 100644
--- a/doc/cmd.rst
+++ b/doc/cmd.rst
@@ -10,9 +10,11 @@ Coverage command line usage
 :history: 20091004T170700, changes for 3.1
 :history: 20091127T200700, changes for 3.2
 :history: 20100223T200600, changes for 3.3
+:history: 20100725T211700, updated for 3.4.
 
 .. highlight:: console
 
+
 When you install coverage.py, a command-line script simply called ``coverage``
 is placed in your Python scripts directory.  Coverage has a number of commands
 which determine the action performed:
diff --git a/doc/config.rst b/doc/config.rst
index 2e0cd766..b0e5bf84 100644
--- a/doc/config.rst
+++ b/doc/config.rst
@@ -5,6 +5,8 @@ Configuration files
 ===================
 
 :history: 20100223T201600, new for 3.3
+:history: 20100725T211700, updated for 3.4.
+
 
 Coverage.py options can be specified in a configuration file.  This makes it
 easier to re-run coverage with consistent settings, and also allows for
diff --git a/doc/excluding.rst b/doc/excluding.rst
index 55acebeb..466f56a7 100644
--- a/doc/excluding.rst
+++ b/doc/excluding.rst
@@ -6,6 +6,7 @@ Excluding code from coverage
 
 :history: 20090613T090500, brand new docs.
 :history: 20100224T200900, updated for 3.3.
+:history: 20100725T211700, updated for 3.4.
 
 
 You may have code in your project that you know won't be executed, and you want
@@ -91,3 +92,10 @@ Here's a list of exclusions I've used::
 Note that when using the ``exclude_lines`` option in a configuration file, you
 are taking control of the entire list of regexes, so you need to re-specify the
 default "pragma: no cover" match if you still want it to apply.
+
+
+Excluding source files
+----------------------
+
+See :ref:`source` for ways to limit what files coverage.py measures or reports
+on.
diff --git a/doc/index.rst b/doc/index.rst
index 094962e7..8c50983b 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -12,6 +12,8 @@ coverage.py
 :history: 20091205T161429, version 3.2 for real.
 :history: 20100224T204700, version 3.3
 :history: 20100306T181500, version 3.3.1
+:history: 20100725T211700, updated for 3.4.
+
 
 Coverage.py is a tool for measuring code coverage of Python programs. It
 monitors your program, noting which parts of the code have been executed, then
diff --git a/doc/subprocess.rst b/doc/subprocess.rst
index 81756810..383c797f 100644
--- a/doc/subprocess.rst
+++ b/doc/subprocess.rst
@@ -5,6 +5,7 @@ Measuring subprocesses
 ======================
 
 :history: 20100224T201800, new for 3.3.
+:history: 20100725T211700, updated for 3.4.
 
 
 Complex test suites may spawn subprocesses to run tests, either to run them in