[adding the ML again]

On 11/21/20 6:15 PM, Reuben Thomas wrote:
> Wow! That's a surprise. It could be clarified, at the same time as answering 
> the question "how do I compare with some
> other time of the reference file?" by adding a little text, for example:
>
>     True if the time of the last access (or status change or data 
> modification)
>     of the current file is more recent than that of the last data modification
>     of the @var{reference} file. -anewer is equivalent to -neweram, -cnewer 
> to -newercm, and -newer to -newermm
>     (@ref{Comparing Timestamps}).
>
>
> Would something like that help?

Sure, thanks.
I added some filling word to avoid to have the '-anewer' at the begin of a 
sentence
(which would look odd).  I also removed the @ref{...} because we are in that 
same
section already.

Pushed at:
https://git.sv.gnu.org/cgit/findutils.git/commit/?id=f65445d23c

Thanks & have a nice day,
Berny
>From f65445d23c902253af96f97d336378a78851b474 Mon Sep 17 00:00:00 2001
From: Bernhard Voelker <m...@bernhard-voelker.de>
Date: Sun, 22 Nov 2020 16:04:40 +0100
Subject: [PATCH] doc: relate -anewer, -cnewer, and -newer to their -newerXY
 equivalents

* doc/find.texi (Comparing Timestamps): Clarify that the above options
are equivalent to the options -neweram, -newercm and -newermm.

Suggested by Reuben Thomas.
---
 doc/find.texi | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/find.texi b/doc/find.texi
index 0d7c8ae8..243fec11 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -1002,6 +1002,8 @@ rm -f /tmp/stamp$$
 True if the time of the last access (or status change or data modification)
 of the current file is more recent than that of the last data modification
 of the @var{reference} file.
+As such, @samp{-anewer} is equivalent to @samp{-neweram},
+@samp{-cnewer} to @samp{-newercm}, and @samp{-newer} to @samp{-newermm}.
 
 If @var{reference} is a symbolic link and the @samp{-H} option or the @samp{-L}
 option is in effect, then the time of the last data modification of the file
-- 
2.29.2

Reply via email to