From 500eccdbe4d55b0cbf48cf264aa4232abd7c23df Mon Sep 17 00:00:00 2001
From: Jim Meyering <jim@meyering.net>
Date: Fri, 7 Sep 2007 10:37:08 +0200
Subject: chmod: don't ignore a dangling symlink

* NEWS: Mention the bug fix.
* src/chmod.c (process_file): Handle the case of FTS_SLNONE,
i.e., give a diagnostic saying we cannot operate on such a file.
* tests/chmod/thru-dangling: Compare new stderr output with expected.
---
 NEWS | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'NEWS')

diff --git a/NEWS b/NEWS
index 6a0f18d9a..93a632c5a 100644
--- a/NEWS
+++ b/NEWS
@@ -70,6 +70,10 @@ GNU coreutils NEWS                                    -*- outline -*-
 
 ** Bug fixes
 
+  chmod no longer ignores a dangling symlink.  Now, chmod fails
+  with a diagnostic saying that it cannot operate on such a file.
+  [bug introduced in coreutils-5.1.0]
+
   cp attempts to read a regular file, even if stat says it is empty.
   Before, "cp /proc/cpuinfo c" would create an empty file when the kernel
   reports stat.st_size == 0, while "cat /proc/cpuinfo > c" would "work",
-- 
cgit v1.2.3-70-g09d2