Hi,
the attached patch removes a duplicate paragraph from find.texi and fixes a
formatting typo. I hope that can also be applied to the 4.4 branch.
Regards
Peter Breitenlohner <[email protected]>
From 41088ce364bd1154b918c838947145320f14377d Mon Sep 17 00:00:00 2001
From: Peter Breitenlohner <[email protected]>
Date: Mon, 3 Aug 2009 11:16:29 +0200
Subject: [PATCH] Remove duplicate paragraph in texinfo
Signed-off-by: Peter Breitenlohner <[email protected]>
---
ChangeLog | 4 ++++
doc/find.texi | 12 +-----------
2 files changed, 5 insertions(+), 11 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 9c3290a..fd14c44 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2009-08-03 Peter Breitenlohner <[email protected]>
+
+ * doc/find.texi: Remove duplicate paragraph and fix a typo.
+
2009-07-18 James Youngman <[email protected]>
Fix up some problems introduced in a manual conflict resolution.
diff --git a/doc/find.texi b/doc/find.texi
index 24ee8a8..5a2a121 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -2826,7 +2826,7 @@ database is zero. The second byte is immediately
followed by the
first database entry. The first entry in the database is not preceded
by any differential count or dummy entry. Instead the differential
count for the first item is assumed to be zero.
-.P
+
Starting with the second entry (if any) in the database, data is
interpreted as for the GNU LOCATE02 format.
@@ -3329,16 +3329,6 @@ that ``exports'' configurations for variable definitions
and uses
another shell script that ``sources'' the configuration file into the
environment and then executes @code{updatedb} in the environment.
-...@code{updatedb} creates and updates the database of file names used by
-...@code{locate}. @code{updatedb} generates a list of files similar to
-the output of @code{find} and then uses utilities for optimizing the
-database for performance. @code{updatedb} is often run periodically
-as a @code{cron} job and configured with environment variables or
-command options. Typically, operating systems have a shell script
-that ``exports'' configurations for variable definitions and uses
-another shell script that ``sources'' the configuration file into the
-environment and then executes @code{updatedb} in the environment.
-
@table @code
@item --findoptions='@var{opti...@dots{}'
Global options to pass on to @code{find}.
--
1.6.4
