Removed trailing whitespace.

Removed trailing whitespace.
* Makefile.am: Removed trailing white space.
* NEWS, build-aux/check-testfiles.sh, build-aux/src-sniff.py,
doc/Makefile.am, doc/find-maint.texi, doc/find.texi, find/Makefile.am,
find/defs.h, find/find.1, find/find.c, find/finddata.c, find/fstype.c,
find/ftsfind.c, find/parser.c, find/pred.c, find/tree.c, find/util.c,
import-gnulib.sh, lib/Makefile.am, lib/buildcmd.c, lib/buildcmd.h,
lib/dircallback.c, lib/dircallback.h, lib/extendbuf.c,
lib/extendbuf.h, lib/findutils-version.c, lib/findutils-version.h,
lib/forcefindlib.c, lib/gnulib-version.h, lib/listfile.c,
lib/modetype.h, lib/nextelem.c, lib/nextelem.h, lib/printquoted.c,
lib/printquoted.h, lib/qmark.c, lib/regexprops.c, lib/regextype.c,
lib/savedirinfo.c, lib/savedirinfo.h, lib/strspn.c, lib/wait.h,
lib/waitpid.c, locate/bigram.c, locate/code.c, locate/locate.1,
locate/locate.c, locate/locatedb.5, locate/locatedb.h,
locate/updatedb.1, locate/updatedb.sh, locate/word_io.c,
m4/findlib.m4, m4/nullsort.m4, m4/withfts.m4, xargs/xargs.1: Likewise.

Signed-off-by: James Youngman <jay@gnu.org>

3 files changed, 11 insertions, 11 deletions

diff --git a/doc/Makefile.am b/doc/Makefile.am
index 2e085531..59938b95 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -1,12 +1,12 @@
 info_TEXINFOS = find.texi find-maint.texi
 find_TEXINFOS = perm.texi getdate.texi regexprops.texi fdl.texi
 find_maint_TEXINFOS = fdl.texi
-MOSTLYCLEANFILES = find.cps 
+MOSTLYCLEANFILES = find.cps
 CLEANFILES = find.txt find_mono.html findutils.texi_html_node.tar.gz
 
-# To build regexprops.texi, we need to build the regexprops program and 
+# To build regexprops.texi, we need to build the regexprops program and
 # run it on the host.  If we are cross compiling, we may not have a native
-# binary.  When this is the case, we use a workaround; don't delete the 
+# binary.  When this is the case, we use a workaround; don't delete the
 # file for 'make clean'.  This fixes Savannah bug #19658.
 if !CROSS_COMPILING
 CLEANFILES += regexprops.texi regexprops-generic.texi
@@ -16,7 +16,7 @@ MAKEINFOTXT = $(MAKEINFO) --plaintext
 
 find.txt: find.texi $(srcdir)/version.texi $(find_TEXINFOS)
 
-# find.txt is a file which we need to know how to build 
+# find.txt is a file which we need to know how to build
 # because it gets put on the www.gnu.org website.
 # This rule is derived from the .texi.html rule.
 .texi.txt:
@@ -34,7 +34,7 @@ find.txt: find.texi $(srcdir)/version.texi $(find_TEXINFOS)
 	fi
 
 
-# find_mono.html is a file which we need to know how to build 
+# find_mono.html is a file which we need to know how to build
 # because it gets put on the www.gnu.org website.
 # This rule is derived from the generic .texi.html rule.
 find_mono.html: find.texi
@@ -54,8 +54,8 @@ find_mono.html: find.texi
 
 # findutils.texi_html_node.tar.gz is a file which we need to know
 # how to build because it gets put on the www.gnu.org website.
-# This rule depends on GNU tar, but it's principally used 
-# by the maintainer, and we don't need to build the file 
+# This rule depends on GNU tar, but it's principally used
+# by the maintainer, and we don't need to build the file
 # for "make all" or "make install" (or even "make check").
 findutils.texi_html_node.tar.gz: find.html
 	tar zcf $@ $<
diff --git a/doc/find-maint.texi b/doc/find-maint.texi
index 49be2652..29f34574 100644
--- a/doc/find-maint.texi
+++ b/doc/find-maint.texi
@@ -487,7 +487,7 @@ tarball you can download.  Instead, the code is simply made available
 by GIT.   The code is also available via @code{git-cvspserver}, but
 we decided not to use this, since @code{import-gnulib.sh} depended on
 @code{cvs update -D}, which at the time @code{git-cvspserver} did not
-support.  
+support.
 
 GNU projects vary in how they interact with Gnulib.  Many import a
 selection of code from Gnulib into the working directory and then
diff --git a/doc/find.texi b/doc/find.texi
index 56d3e32c..765cd6f5 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -2530,8 +2530,8 @@ The response to the prompt is matched against a pair of regular
 expressions to determine if it is a yes or no response.  These regular
 expressions are obtained from the system@footnote{@code{nl_langinfo} items YESEXPR and NOEXPR are used}
 if the POSIXLY_CORRECT environment variable is set and the system has
-such patterns available. 
-Otherwise, @code{find}'s message translations are used.  
+such patterns available.
+Otherwise, @code{find}'s message translations are used.
 In either case, the LC_MESSAGES environment variable
 will determine the regular expressions used to determine if the answer
 is affirmative or negative.  The interpretation of the regular
@@ -4652,7 +4652,7 @@ that we descend no further.
 
 For large, complex trees like the Linux kernel, this will prevent
 searching a large portion of the structure, saving a good deal of
-time.  
+time.
 
 
 @node Security Considerations