From 9f7f25d31c1edb2a34b9dd4d518c102c6152575f Mon Sep 17 00:00:00 2001 From: jay Date: Sat, 8 Mar 2008 21:38:25 +0000 Subject: [PATCH] Typo fix from Jim Meyering --- ChangeLog | 6 ++++++ doc/find-maint.texi | 8 ++++---- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index cdae6bf..f92651c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2008-03-08 Jim Meyering + + Fix doc typos. + * doc/find-maint.texi (Security): s/ongest/longest/ + (Making Releases): s/the the/the/ + 2008-02-15 Eric Blake Avoid compiler warnings. diff --git a/doc/find-maint.texi b/doc/find-maint.texi index 5c7c6b2..05d16c1 100644 --- a/doc/find-maint.texi +++ b/doc/find-maint.texi @@ -23,7 +23,7 @@ be made and tested, and what resources exist to help developers. This is edition @value{EDITION}, for findutils version @value{VERSION}. -Copyright @copyright{} 2007 Free Software Foundation, Inc. +Copyright @copyright{} 2007, 2008 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 @@ -792,7 +792,7 @@ becomes available. Here is an example alert:- @smallexample GNU findutils heap buffer overrun (potential privilege escalation) -$Revision: 1.5 $; $Date: 2007/11/29 11:07:19 $ +$Revision: 1.6 $; $Date: 2008/03/08 21:38:25 $ I. BACKGROUND @@ -852,7 +852,7 @@ All existing releases of findutils are affected. Installations ------------- -To discover the ongest path name on a given system, you can use the +To discover the longest path name on a given system, you can use the following command (requires GNU findutils and GNU coreutils): @verbatim @@ -1125,7 +1125,7 @@ and @file{NEWS} files to advance the release numbers. For example, if you have just released @samp{4.6.2}, bump the release number to @samp{4.6.3-CVS}. The point of the @samp{-CVS} suffix here is that a findutils binary built from CVS will bear a release number indicating -it's not built from the the ``official'' source release. +it's not built from the ``official'' source release. @item Close bugs; any bugs recorded on Savannah which were fixed in this release should now be marked as closed. Update the @samp{Fixed Release} field of these bugs appropriately and make sure the -- 2.11.4.GIT