+2017-08-16 Bruno Haible <bruno@clisp.org>
+
+ rename, renameat: Update doc regarding NetBSD.
+ * doc/posix-functions/rename.texi: Clarify that when using
+ -D_XOPEN_SOURCE=500 on NetBSD 7.0, the hard link bug is gone.
+ * doc/posix-functions/renameat.texi: Be more precise about NetBSD
+ version.
+
2017-08-15 Paul Eggert <eggert@cs.ucla.edu>
renameat2: port better to macOS
@item
This function incorrectly reduces the link count when comparing two
spellings of a hard link on some platforms:
-NetBSD 1.6, Cygwin 1.5.x.
+NetBSD 1.6, NetBSD 7.0 without @code{-D_XOPEN_SOURCE=500}, Cygwin 1.5.x.
@item
This function will not always replace an existing destination on some
platforms:
@code{ENOTDIR} if either argument is a symlink with a trailing slash:
glibc, OpenBSD, Cygwin 1.7.
@item
-POSIX requires that @code{renameat} do nothing and return 0 if the
+POSIX requires that @code{rename} do nothing and return 0 if the
source and destination are hard links to the same file. This behavior
is counterintuitive, and on some systems @code{renameat} is a no-op in
this way only if the source and destination identify the same
@file{./f} to @file{f} is a no-op, renaming @file{f} to @file{g}
deletes @file{f} when @file{f} and @file{g} are hard links to the same
file:
-NetBSD.
+NetBSD 7.0.
@item
After renaming a non-empty directory over an existing empty directory,
the old directory name is still visible through the @code{stat} function
@file{./f} to @file{f} is a no-op, renaming @file{f} to @file{g}
deletes @file{f} when @file{f} and @file{g} are hard links to the same
file:
-NetBSD.
+NetBSD 7.0.
@item
After renaming a non-empty directory over an existing empty directory,
the old directory name is still visible through the @code{stat} function