doc: minor grammar change about a change in the past

In the description of -name patterns matching "hidden" files, i.e.,
those beginning with a dot, avoid talking in the future.
The change was back in version 4.2.2.
Maybe we should drop this hint about historic behavior at all.

* doc/find.texi (Base Name Patterns): Remove the word "will".
* find/find.1 (.SH STANDARDS CONFORMANCE): Likewise.
(.SH HISTORY): Likewise.
This commit is contained in:
Bernhard Voelker 2020-12-30 09:53:32 +01:00
parent 9302afb984
commit 9b7edc6884
2 changed files with 4 additions and 4 deletions

View File

@ -400,8 +400,8 @@ Notice that the wildcard must be enclosed in quotes in order to
protect it from expansion by the shell.
As of findutils version 4.2.2, patterns for @samp{-name} and
@samp{-iname} will match a file name with a leading @samp{.}. For
example the command @samp{find /tmp -name \*bar} will match the file
@samp{-iname} match a file name with a leading @samp{.}. For
example the command @samp{find /tmp -name \*bar} match the file
@file{/tmp/.foobar}. Braces within the pattern (@samp{@{@}}) are not
considered to be special (that is, @code{find . -name 'foo@{1,2@}'}
matches a file named @file{foo@{1,2@}}, not the files @file{foo1} and

View File

@ -1849,7 +1849,7 @@ This option is supported, but POSIX conformance depends on the
POSIX conformance of the system's
.BR fnmatch (3)
library function. As of findutils-4.2.2, shell metacharacters
(`*', `?' or `[]' for example) will match a leading `.', because
(`*', `?' or `[]' for example) match a leading `.', because
IEEE PASC interpretation 126 requires this.
This is a change from previous versions of findutils.
@ -2461,7 +2461,7 @@ may not have been performed.
.
.SH "HISTORY"
As of findutils-4.2.2, shell metacharacters (`*', `?' or `[]' for
example) used in filename patterns will match a leading `.', because
example) used in filename patterns match a leading `.', because
IEEE POSIX interpretation 126 requires this.
.P
As of findutils-4.3.3,