Bug#796822: lintian: Update documentation to reflect check-tag's replacement

[Chris Lamb <lamby@debian.org>]

Package: lintian
Version: 2.5.36.1
Severity: wishlist
Tags: patch

Hi,

Patch attached to update various bits of the documentation to reflect
check-tag's replacement.


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

From 00d9d2d1bae068553f213b40c3212cb192ab0acc Mon Sep 17 00:00:00 2001
From: Chris Lamb <lamby@debian.org>
Date: Mon, 24 Aug 2015 21:28:18 +0200
Subject: [PATCH] t: Update documentation to reflect check-tag's replacement

Signed-off-by: Chris Lamb <lamby@debian.org>
---
 t/changes/README | 2 +-
 t/debs/README    | 2 +-
 t/runtests       | 4 ++--
 t/source/README  | 2 +-
 t/tests/README   | 7 ++++---
 5 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/t/changes/README b/t/changes/README
index 547bdaf..2ee06de 100644
--- a/t/changes/README
+++ b/t/changes/README
@@ -53,7 +53,7 @@ Give only the test name, not the full path.
 It's often more useful to run every test that is relevant to a
 particular tag.  To do that, run:
 
-    debian/rules check-tag tag=<tag>
+    debian/rules runtests onlyrun=tag:<tag>
 
 This will run all tests that list that tag in the .tags file.
 
diff --git a/t/debs/README b/t/debs/README
index 4d01906..541393f 100644
--- a/t/debs/README
+++ b/t/debs/README
@@ -87,7 +87,7 @@ To run a specific test case, run:
 It's often more useful to run every test that is relevant to a
 particular tag.  To do that, run:
 
-    debian/rules check-tag tag=<tag>
+    debian/rules runtests onlyrun=tag:<tag>
 
 This will run all tests that list that tag in the tags file.
 
diff --git a/t/runtests b/t/runtests
index e93a0fe..6000d52 100755
--- a/t/runtests
+++ b/t/runtests
@@ -21,8 +21,8 @@
 # MA 02110-1301, USA.
 
 # The harness for Lintian's new test suite.  Normally run through the runtests
-# or check-tag targets in debian/rules.  For detailed information on the test
-# suite layout and naming conventions, see t/tests/README.
+# targets in debian/rules.  For detailed information on the test suite layout
+# and naming conventions, see t/tests/README.
 #
 # The build output is directed to build.pkgname in the testing-directory.
 
diff --git a/t/source/README b/t/source/README
index a268f4c..0dc6d21 100644
--- a/t/source/README
+++ b/t/source/README
@@ -80,7 +80,7 @@ To run a specific test case, run:
 It's often more useful to run every test that is relevant to a
 particular tag.  To do that, run:
 
-    debian/rules check-tag tag=<tag>
+    debian/rules runtests onlyrun=tag:<tag>
 
 This will run all tests that list that tag in the tags file.
 
diff --git a/t/tests/README b/t/tests/README
index 19b9dde..cfb5759 100644
--- a/t/tests/README
+++ b/t/tests/README
@@ -237,7 +237,7 @@ file name, not the full path.
 It's often more useful to run every test that is relevant to a
 particular tag.  To do that, run:
 
-    debian/rules check-tag tag=<tag>
+    debian/rules runtests onlyrun=tag:<tag>
 
 This will run all tests that list that tag in either Test-For or
 Test-Against.
@@ -270,8 +270,9 @@ issued.
 
 Be sure to use Test-For and Test-Against for tags that are targets of
 a particular test case.  The test harness will ensure that the test
-case behaves correctly, and that metadata is used for the check-tag
-target and when checking test coverage.
+case behaves correctly, and that metadata is used for the runtests
+target (when called with the onlyrun=tag:<tag> filter) and when checking test
+coverage.
 
 The test template uses debhelper 7.  Use debhelper 7 features whenever
 possible rather than replacing the rules file with a more verbose one.
-- 
2.5.0