[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug#470308: findutils: fixes for the info file
From: |
Justin Pryzby |
Subject: |
Re: Bug#470308: findutils: fixes for the info file |
Date: |
Mon, 10 Mar 2008 15:47:02 -0400 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
On Mon, Mar 10, 2008 at 04:59:15PM +0000, James Youngman wrote:
> On Mon, Mar 10, 2008 at 4:05 PM, Justin Pryzby
> <address@hidden> wrote:
> > - Symbolic links are different to "hard links" in the sense that you
> > + Symbolic links are different than "hard links" in the sense that you
>
> No. The phrase "different to" is correct, but it you prefer to be
> pedantic, then "different from" would probably be the ideal phrasing.
On reflection, I agree.
> > - Print search results when they normally would not, because of the
> > - presence of `--statistics' (`-S') or `--count' (`-c').
> > + Print search results when they normally wouldn't be due to
> > + use of `--statistics' (`-S') or `--count' (`-c').
>
> Likewise (and some other changes).
What else?
> However, "find.info" is not the source file; it is generated from find.texi.
Doh.
> You can get the current upstream source from
> http://savannah.gnu.org/cvs/?group=findutils. Please send your
> patch to address@hidden or to address@hidden
I include a patch against 4.2.33-1 (Debian). A few changes weren't
necessary in that (more recent) version:
-This behaviour is different to
-This is different to `-prune'
(2 lines)
-do no appear
Justin
--- findutils-4.2.28.orig/doc/find.texi
+++ findutils-4.2.28/doc/find.texi
@@ -615,7 +615,7 @@
links listed on the command line are dereferenced, but other symbolic
links are not.
-Symbolic links are different to ``hard links'' in the sense that you
+Symbolic links are different from ``hard links'' in the sense that you
need permissions upon the linked-to file in order to be able to
dereference the link. This can mean that even if you specify the
@samp{-L} option, @code{find} may not be able to determine the
@@ -893,7 +893,7 @@
The `b' suffix always considers blocks to be 512 bytes. This is not
affected by the setting (or non-setting) of the POSIXLY_CORRECT
-environment variable. This behaviour is different to the behaviour of
+environment variable. This behaviour is different from the behaviour of
the @samp{-ls} action). If you want to use 1024-byte units, use the
`k' suffix instead.
@@ -2222,7 +2222,7 @@
Here, the first invocation of @code{xargs} has no input line length
limit because it doesn't use the @samp{-I} option. The second
invocation of @code{xargs} does have such a limit, but we have ensured
-that the it never encounters a line which is longer than it can
+that it never encounters a line which is longer than it can
handle.
This is not an ideal solution. Instead, the @samp{-I} option should
@@ -2801,14 +2801,14 @@
@item --null
@itemx -0
Results are separated with the ASCII NUL character rather than the
-newline character. To get the full benefit of the use of this option,
+newline character. To get the full benefit of this option,
use the new @code{locate} database format (that is the default
anyway).
@item --print
@itemx -p
-Print search results when they normally would not, because of the
-presence of @samp{--statistics} (@samp{-S}) or @samp{--count}
+Print search results when they normally would not be due to
+use of @samp{--statistics} (@samp{-S}) or @samp{--count}
(@samp{-c}).
@item --wholename
@@ -4131,7 +4131,7 @@
If your system supports the O_NOFOLLOW flag @footnote{GNU/Linux
(kernel version 2.1.126 and later) and FreeBSD (3.0-CURRENT and later)
support this} to the @code{open(2)} system call, @code{find} uses it
-when safely changing directory. The target directory is first opened
+to safely change directories. The target directory is first opened
and then @code{find} changes working directory with the
@code{fchdir()} system call. This ensures that symbolic links are not
followed, preventing the sort of race condition attack in which use
@@ -4405,7 +4405,7 @@
@item Warning: filesystem /path/foo has recently been mounted
@itemx Warning: filesystem /path/foo has recently been unmounted
These messages might appear when @code{find} moves into a directory
-and finds that the device number and inode are different to what it
+and finds that the device number and inode are different from what it
expected them to be. If the directory @code{find} has moved into is
on an network filesystem (NFS), it will not issue this message, because
@code{automount} frequently mounts new filesystems on directories as
@@ -4445,7 +4445,7 @@
another location in the same filesystem. This may or may not have been done
maliciously. In any case, @code{find} stops at this point
to avoid traversing parts of the filesystem that it wasn't
-intended. You can use @code{ls -li} or @code{find /path -inum
+intended to. You can use @code{ls -li} or @code{find /path -inum
12345 -o -inum 67893} to find out more about what has happened.
@item sanity check of the fnmatch() library function failed.