+2006-01-26 Paul Eggert <eggert@cs.ucla.edu>
+
+ * fts.c (diropen): Open with O_NOCTTY | O_NONBLOCK too. Don't
+ attempt to open for write; this always fails, at least on POSIX
+ hosts. This reinstates the 2006-01-09 change, which was
+ inadvertently removed.
+
+2006-01-26 Bruno Haible <bruno@clisp.org>
+ Paul Eggert <eggert@cs.ucla.edu>
+
+ * stdbool_.h (_Bool)
+ [(! (defined __cplusplus || defined __BEOS__)
+ && !defined __GNUC__
+ && !(defined __HP_cc || defined __xlc__
+ || (defined __SUNPRO_C && (__SUNPRO_C < 0x550 || __STDC__ == 1))
+ || defined __sgi))]:
+ #define to signed char in these cases too; this simplifies
+ the code (so that we don't have to worry about HP-UX, AIX, SunPRO,
+ etc., separately) and makes it more conservative.
+
+2006-01-21 Jim Meyering <jim@meyering.net>
+
+ Sync from the stable (b5) branch of coreutils:
+
+ * fts.c (fts_children): Don't let close() clobber errno from
+ failed fchdir().
+
+ * fts.c (fts_stat): When following a symlink-to-directory,
+ don't necessarily interpret stat-fails+lstat-succeeds as indicating
+ a dangling symlink. That can also happen at least for ELOOP.
+ The fix: return FTS_SLNONE only when the stat errno is ENOENT.
+ FYI, this bug predates the inclusion of fts.c in coreutils.
+
+ * fts.c (fts_open): Put new maxarglen declaration and uses
+ in their own block, so pre-c99 compilers don't object.
+
+ Avoid the double-free (first in fts_read, second in fts_close) that
+ would occur when an `active' directory is made inaccessible (e.g.,
+ via chmod a-x) during a traversal.
+ * fts.c (fts_read): After a failed fchdir, update sp->fts_cur
+ before returning. Reproduce this failure by
+ mkdir -p a/b; cd a; chmod a-x . b
+ Reported by Stavros Passas.
+
+2006-01-25 Sergey Poznyakoff <gray@gnu.org.ua>
+
+ * argp-namefrob.h: Bugfix. Remove stray #
+
2006-01-25 Bruno Haible <bruno@clisp.org>
* stdbool_.h (_Bool) [IRIX cc]: Define as 'signed char', to avoid
projects / pspp / blobdiff