* doc/find.texi: Do the above in various places.
* find/find.1: Likewise.
* xargs/xargs.1: Likewise.
---
doc/find.texi | 18 +++++++++---------
find/find.1 | 4 ++--
xargs/xargs.1 | 5 +++--
3 files changed, 14 insertions(+), 13 deletions(-)
diff --git a/doc/find.texi b/doc/find.texi
index cc0e47e1..fd0ebc57 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -509,8 +509,8 @@ for a match with @samp{-name} will never include a slash, so
@samp{-name a/b} will never match anything (you probably need to use
@samp{-path} instead).
-The @samp{-iname} option appeared first only in POSIX Issue 8 while
-GNU @code{find} supports it since version 3.8 (1993).
+The @samp{-iname} option appeared first in POSIX Issue 8 (IEEE Std 1003.1-2024)
+while GNU @code{find} supports it since version 3.8 (1993).
@end deffn
@@ -535,8 +535,8 @@ arguments ending in @samp{/} will match nothing (except
perhaps a
start point specified on the command line).
The name @samp{-wholename} is GNU-specific, but @samp{-path} is more
-portable; it is supported by HP-UX @code{find} and is part of the
-POSIX 2008 standard.
+portable: the latter is supported by HP-UX @code{find} and is part of the
+POSIX standard (since IEEE Std 1003.1-2008).
@end deffn
@@ -2588,8 +2588,8 @@ can process file names generated this way by giving the
@samp{-0} or
@samp{--null} option to GNU @code{xargs}, GNU @code{tar}, GNU
@code{cpio}, or @code{perl}.
-Both @code{find . -print0} and @code{xargs -0} will be
-POSIX-conforming, starting from the currently-expected Issue 8.
+Both @code{find . -print0} and @code{xargs -0} are
+POSIX-conforming since Issue 8 (IEEE Std 1003.1-2024).
@deffn Action -print0
True; print the entire file name on the standard output, followed by a
@@ -4759,7 +4759,7 @@ portable construct. Support for @samp{-print0} is not
universal.
Although some other versions of Unix (notably BSD-derived ones)
support @samp{-print0}, this is only required in POSIX from Issue 8
-(published 2024-06-14). So, is there a more universal mechanism?
+(IEEE Std 1003.1-2024). So, is there a more universal mechanism?
@subsection Going back to @code{-exec}
@@ -5647,8 +5647,8 @@ The only ways to avoid this problem are either to avoid
all use of
available) @samp{find -execdir}, or to use the @samp{-0} option, which
ensures that @code{xargs} considers file names to be separated by
ASCII NUL characters rather than whitespace. However, useful as this
-option is, the POSIX standard did not make it mandatory prior to Issue
-8.
+option is, the POSIX standard did not make it mandatory prior to
+Issue 8 (IEEE Std 1003.1-2024).
POSIX also specifies that @code{xargs} without @code{-0} interprets quoting
and trailing
whitespace specially in filenames, too. This means that using
diff --git a/find/find.1 b/find/find.1
index bb07efe2..adc15282 100644
--- a/find/find.1
+++ b/find/find.1
@@ -2743,10 +2743,10 @@ Feature Added in Also occurs in
\-ignore_readdir_race 4.2.0
\-fls 4.0
\-ilname 3.8
-\-iname 3.8 POSIX (from Issue 8)
+\-iname 3.8 POSIX (from Issue 8, IEEE Std 1003.1\-2024)
\-ipath 3.8
\-iregex 3.8
-\-print0 2.0 POSIX (from Issue 8)
+\-print0 2.0 POSIX (from Issue 8, IEEE Std 1003.1\-2024)
.TE
.P
The syntax
diff --git a/xargs/xargs.1 b/xargs/xargs.1
index d238cfc0..02e17da2 100644
--- a/xargs/xargs.1
+++ b/xargs/xargs.1
@@ -73,7 +73,8 @@ whitespace, and the quotes and backslash are not special
(every
character is taken literally).
Disables the end-of-file string, which is treated like any other argument.
Useful when input items might contain white space, quote marks, or backslashes.
-The GNU find (and from Issue 8, POSIX) \-print0 option produces input suitable
for this mode.
+The GNU find (and from POSIX Issue 8, IEEE Std 1003.1\-2024)
+\-print0 option produces input suitable for this mode.
.TP
.BI "\-a " file ", \-\-arg\-file=" file
@@ -452,7 +453,7 @@ The long-standing
.B \-0
option of
.B xargs
-will be included in Issue 8 of the POSIX standard.
+appeared first in Issue 8 (IEEE Std 1003.1\-2024) of the POSIX standard.
As of GNU xargs version 4.2.9, the default behaviour of
.B xargs
--
2.51.1
