Change comments: say bug present up to coreutils-6.9, not fixed in 6.10.

* tests/cut/Test.pm: Adjust comment.
* tests/misc/cut: Likewise.
* tests/misc/ls-misc: Likewise.
* tests/misc/od: Likewise.
* tests/misc/stty-invalid: Likewise.
* tests/tr/Test.pm: Likewise.

4 files changed, 9 insertions, 9 deletions

diff --git a/tests/misc/cut b/tests/misc/cut
index 0a8ae3ae6..2fc4bed05 100755
--- a/tests/misc/cut
+++ b/tests/misc/cut
@@ -46,11 +46,11 @@ my @Tests =
    # Provoke a double-free in cut from coreutils-6.7.
    ['dbl-free', '-f2-', {IN=>{f=>'x'}}, {IN=>{g=>'y'}}, {OUT=>"x\ny\n"}],
 
-   # This failed (as it should) even before coreutils-6.10,
-   # but cut from 6.10 produces a more useful diagnostic.
+   # This failed (as it should) even before coreutils-6.9.90,
+   # but cut from 6.9.90 produces a more useful diagnostic.
    ['zero-1', '-b0',   {ERR=>$diag}, {EXIT => 1} ],
 
-   # Before coreutils-6.10, specifying a range of 0-2 was not an error.
+   # Up to coreutils-6.9, specifying a range of 0-2 was not an error.
    # It was treated just like "-2".
    ['zero-2', '-f0-2', {ERR=>$diag}, {EXIT => 1} ],
   );
diff --git a/tests/misc/ls-misc b/tests/misc/ls-misc
index 1e4f327f9..9e0706577 100755
--- a/tests/misc/ls-misc
+++ b/tests/misc/ls-misc
@@ -138,11 +138,11 @@ my @Tests =
 				 {OUT => "\e[0m\e[01;36md\e[0m\@\n\e[m"},
 				  $slink_d, $unlink_d],
 
-     # Test for a bug fixed in coreutils-6.10.
+     # Test for a bug fixed after coreutils-6.9.
      ['sl-target', '--color=always d',
       {OUT => "\e[0m\e[01;34mX\e[0m\n\e[m"}, $target, $target2],
 
-     # Test for another bug fixed in coreutils-6.10.
+     # Test for another bug fixed after coreutils-6.9.
      # This one bites only for a system/file system with d_type support.
      ['sl-dangle', '--color=always d',
       {OUT => "\e[0m\e[40;31;01mX\e[0m\n\e[m"},
diff --git a/tests/misc/od b/tests/misc/od
index d827c2b07..bf41c3846 100755
--- a/tests/misc/od
+++ b/tests/misc/od
@@ -59,7 +59,7 @@ my $proc_file_byte_count = $len;
 my @Tests =
     (
      # Skip the exact length of the input file.
-     # Before coreutils-6.10, this would ignore the "-j 1".
+     # Up to coreutils-6.9, this would ignore the "-j 1".
      ['j-bug1', '-c -j 1 -An', {IN=>{g=>'a'}}, {OUT=>''}],
      ['j-bug2', '-c -j 2 -An', {IN=>{g=>'a'}}, {IN=>{h=>'b'}}, {OUT=>''}],
      # Skip the sum of the lengths of the first three inputs.
diff --git a/tests/misc/stty-invalid b/tests/misc/stty-invalid
index a2a636d06..d35159475 100755
--- a/tests/misc/stty-invalid
+++ b/tests/misc/stty-invalid
@@ -30,14 +30,14 @@ fail=0
 saved_state=`stty -g` || fail=1
 stty $saved_state || fail=1
 
-# Before coreutils-6.10, if stty were given an argument with 35 colons
+# Before coreutils-6.9.90, if stty were given an argument with 35 colons
 # separating 36 hexadecimal strings, stty would fail to diagnose as invalid
 # any number that was out of range as long as sscanf happened to
 # overflow/wrap it back into the range of the corresponding type (either
 # tcflag_t or cc_t).
 
-# For each of the following, before 6.10, stty would fail to
-# diagnose the error on at least Solaris 10.
+# For each of the following, with coreutils-6.9 and earlier,
+# stty would fail to diagnose the error on at least Solaris 10.
 hex_2_64=10000000000000000
 stty `echo $saved_state |sed 's/^[^:]*:/'$hex_2_64:/`     2>/dev/null && fail=1
 stty `echo $saved_state |sed 's/:[0-9a-f]*$/:'$hex_2_64/` 2>/dev/null && fail=1