summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2012-12-08 12:04:14 -0800
committerJim Meyering <jim@meyering.net>2012-12-09 15:08:36 -0800
commit4f62d2fe28abe9d7b59b2fc50b59db4d8f2a3853 (patch)
tree8ccbf5868b80faff05a465cf559aa2fe94a85936 /NEWS
parent62543570d72b756a3b04ca9d1ebec6f4dd2eea4b (diff)
downloadcoreutils-4f62d2fe28abe9d7b59b2fc50b59db4d8f2a3853.tar.xz
tests: add test case and note that last week's cut change is a bug fix
* tests/misc/cut-huge-to-eol-range.sh: New test, showing that the change in v8.20-51-g7d03466 is a bug fix after all. * tests/local.mk (all_tests): Add it. * NEWS (Bug fixes): Mention it.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS4
1 files changed, 4 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 6576b503f..e22d3a9e5 100644
--- a/NEWS
+++ b/NEWS
@@ -13,6 +13,10 @@ GNU coreutils NEWS -*- outline -*-
cp --no-preserve=mode now no longer exits non-zero.
[bug introduced in coreutils-8.20]
+ cut with a range like "N-" no longer allocates N/8 bytes. That buffer
+ would never be used, and allocation failure could cause cut to fail.
+ [bug introduced in coreutils-8.10]
+
cut no longer accepts the invalid range 0-, which made it print empty lines.
Instead, cut now fails and emits an appropriate diagnostic.
[This bug was present in "the beginning".]