fts: fts_open: do not let an empty string cause immediate failure

[pspp] / ChangeLog

diff --git a/ChangeLog b/ChangeLog
index 0f130f5596f66122daf223337e070ffc3cb2438d..6eec830ec368ab78e5b08b8c23c487b05471f7f6 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,31 @@
+2009-12-01  Jim Meyering  <meyering@redhat.com>
+
+       fts: fts_open: do not let an empty string cause immediate failure
+       This is required in support of GNU rm, for which the command
+       "rm A '' B" must process and remove both A and B, in spite of
+       the empty string argument.
+       * lib/fts.c (fts_open): Do not let the presence of an empty string
+       cause fts_open to fail immediately.  Most fts-using tools must be
+       able to process all arguments, in order, and can be expected to
+       diagnose such arguments themselves.
+
+2009-11-30  Eric Blake  <ebb9@byu.net>
+
+       utimens: fix compilation error
+       * lib/utimens.c (lutimens) [!HAVE_UTIMENSAT && HAVE_LUTIMES]:
+       Declare variable at right scope.
+
+2009-11-29  Jim Meyering  <meyering@redhat.com>
+
+       bootstrap: handle perl-5.11's changed --version output
+       * build-aux/bootstrap (get_version): Handle perl separately,
+       since perl-5.11's --version output is different.
+
 2009-11-28  Jim Meyering  <meyering@redhat.com>
 
+       userspec: depend on the inttostr module, too
+       * modules/userspec (Depends-on): Add inttostr.
+
        userspec: disallow an ID that maps to (uid_t)-1 or (gid_t)-1
        * lib/userspec.c (parse_with_separator): Do not accept a user ID
        number of MAXUID when it evaluates to (uid_t) -1.