X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Ffaq.texi;h=1e399a0b2366ee68fececc93785982a8174dd3da;hb=2cea0c64b5a0240bfe6746a98a5b350812edb96d;hp=790101a94f7faa1a66b22679e8575f666347c812;hpb=97d77b238d1909ce2e6d377602de797be8a08ac6;p=goredo.git

diff --git a/doc/faq.texi b/doc/faq.texi
index 790101a..1e399a0 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -4,9 +4,9 @@
 @anchor{Stamping}
 @section Hashing and stamping
 
-All targets are checksummed if target's @file{ctime} differs from the
-previous one, or @env{REDO_INODE_NO_TRUST} environment variable is set.
-@command{apenwarr/redo} gives
+All targets are checksummed if target's size, @code{ctime}/@code{mtime}
+differs from the previous one (depending on @ref{OOD, @env{$REDO_INODE_TRUST}}
+value). @command{apenwarr/redo} gives
 @url{https://redo.readthedocs.io/en/latest/FAQImpl/#why-not-always-use-checksum-based-dependencies-instead-of-timestamps, many reasons}
 why every time checksumming is bad, but in my opinion in practice all of
 them do not apply.
@@ -19,10 +19,8 @@ them do not apply.
 @item If you really wish to produce an empty target file, just touch @file{$3}
 @end itemize
 
-DJB's proposal with both @file{stdout} and @file{$3} gives that ability
-to control your desired behaviour. Those who do not capture
-@file{stdout} -- failed. Those who create an empty file if no
-@file{stdout} was written -- failed.
+Those who create an empty file if no @file{stdout} was written -- failed
+implementation.
 
 redo is a tool to help people. Literally all targets can be safely
 @code{redo-stamp < $3}-ed, reducing false positive out-of-dates. Of