NEWS: Remove the now-untrue statement about cp vs. dangling symlinks

diff --git a/ChangeLog b/ChangeLog
index 3d0f9af..cd3047a 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2007-12-01  Jim Meyering  <meyering@redhat.com>
 
+       * NEWS: Remove the now-untrue statement about cp vs. dangling symlinks
+
        Change release procedure: tag *before* running e.g., "make stable".
        * Makefile.maint (vc-dist): Don't tag.  Now, you must apply the tag
        before running "make beta", "make stable", etc.

diff --git a/NEWS b/NEWS
index 8df1b87..dee4a65 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -101,16 +101,14 @@ GNU coreutils NEWS                                    -*- outline -*-
   reports stat.st_size == 0, while "cat /proc/cpuinfo > c" would "work",
   and create a nonempty one. [bug introduced in coreutils-6.0]
 
-  cp no longer fails to write through a dangling symlink
-  [bug introduced in coreutils-6.7].  cp --parents no
-  longer mishandles symlinks to directories in file name
-  components in the source, e.g., "cp --parents symlink/a/b
-  d" no longer fails.  Also, 'cp' no longer considers a
-  destination symlink to be the same as the referenced file when
-  copying links or making backups.  For example, if SYM is a symlink
-  to FILE, "cp -l FILE SYM" now reports an error instead of silently
-  doing nothing.  The behavior of 'cp' is now better documented when
-  the destination is a symlink.
+  cp --parents no longer mishandles symlinks to directories in file
+  name components in the source, e.g., "cp --parents symlink/a/b d"
+  no longer fails.  Also, 'cp' no longer considers a destination
+  symlink to be the same as the referenced file when copying links
+  or making backups.  For example, if SYM is a symlink to FILE,
+  "cp -l FILE SYM" now reports an error instead of silently doing
+  nothing.  The behavior of 'cp' is now better documented when the
+  destination is a symlink.
 
   "cp -i --update older newer" no longer prompts; same for mv