From 59bd26d8797bf38d1ed685a4a3f38493d3ecd96f Mon Sep 17 00:00:00 2001 From: jay Date: Sun, 9 Mar 2008 11:31:52 +0000 Subject: [PATCH] Fix bug #20873, * matches / and leading . in file names --- ChangeLog | 6 ++++++ NEWS | 5 +++++ doc/find.texi | 9 +++++++++ 3 files changed, 20 insertions(+) diff --git a/ChangeLog b/ChangeLog index 0447ae9..1f73281 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2008-03-09 James Youngman + + Fix (documentation) bug #20873, / and . in file names for -path. + * doc/find.texi (Full Name Patterns): Mention that * in the "find + -path" pattern will match both / and leading dots. + 2008-03-08 Jim Meyering Fix doc typos. diff --git a/NEWS b/NEWS index 01f2005..70d91e6 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,11 @@ GNU findutils NEWS - User visible changes. -*- outline -*- (allout) * Major changes in release 4.3.14-CVS +** Documentation Fixes + +#20873: Indicate that * matches / and leading dot in filenames for +"find -path". + * Major changes in release 4.3.13, 2008-02-14 ** Bug Fixes diff --git a/doc/find.texi b/doc/find.texi index dd14f1e..1d5f6ab 100644 --- a/doc/find.texi +++ b/doc/find.texi @@ -450,6 +450,15 @@ $ find /tmp/foo -path /tmp/foo/bar -print Notice that the second @code{find} command prints nothing, even though @file{/tmp/foo/bar} exists and was examined by @code{find}. +Unlike file name expansion on the command line, a @samp{*} in the pattern +will match both @samp{/} and leading dots in file names: + +@example +$ find . -path '*f' +./quux/bar/baz/f +$ find . -path '*/*config' +./quux/bar/baz/.config +@end example @deffn Test -regex expr -- 2.11.4.GIT