Fix undesired error exit on receiving SIGPIPE.

[chaz/tar] / NEWS

diff --git a/NEWS b/NEWS
index f53f8a9ebe5ed63624d8b61e5c8a2b86816b635b..8b55ece0a025cef8934c3482e52664fc7b3354f2 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,9 +1,24 @@
-GNU tar NEWS - User visible changes. 2010-03-11
+GNU tar NEWS - User visible changes. 2010-03-20
 Please send GNU tar bug reports to <bug-tar@gnu.org>
 
 \f
 
-* --test-label behavior
+* Bugfixes.
+
+** Spurious error diagnostics on broken pipe.
+
+When receiving SIGPIPE, tar would exit with error status and
+"write error" diagnostics. In particular, this occurred if
+invoked as in the example below:
+
+   tar tf archive.tar | head -n 1
+
+** --remove-files
+
+Tar --remove-files failed to remove a directory which contained
+symlinks to another files within that directory.
+
+** --test-label behavior
 
 In case of a mismatch, `tar --test-label LABEL' exits with code 1,
 not 2 as it did in previous versions.
@@ -18,7 +33,7 @@ Several volume labels may be specified in a command line, e.g.:
 In this case, tar exits with code 0 if any one of the arguments
 matches the actual volume label.
 
-* --label used with --update
+** --label used with --update
 
 The `--label' option can be used with `--update' to prevent accidental
 update of an archive: