X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Ffeatures.texi;h=13530aec4502f43def54f4d2c8002564ae92f58b;hb=2cea0c64b5a0240bfe6746a98a5b350812edb96d;hp=48c9adcfd28dddb9dad6773a593c813515519a00;hpb=c41fe0fbd726f397636b569161f286821e221885;p=goredo.git

diff --git a/doc/features.texi b/doc/features.texi
index 48c9adc..13530ae 100644
--- a/doc/features.texi
+++ b/doc/features.texi
@@ -13,11 +13,19 @@ implementations.
     @item check that generated target was not modified "externally" outside
       the redo, preventing its overwriting, but continuing the build
     @end itemize
+@item recursive, indented and serialized logs display ability, with
+    priority to the depth and bad return codes, like in @command{apenwarr/redo},
+    thanks to @url{https://apenwarr.ca/log/20181106, apenwarr's article}
+@item all environment variables, working directory, command line
+    arguments, start/finish times, duration, participated PIDs, return
+    codes can be saved for later investigation
 @item targets, dependency information and their directories are explicitly
   synced (can be disabled, should work faster)
-@item file's change is detected by comparing its size, @code{ctime} (if
-    @env{REDO_INODE_NO_TRUST} environment variable is not set) and
-    @url{https://github.com/BLAKE3-team/BLAKE3, BLAKE3} hash
+@item file's change is detected by comparing its size, and
+    @url{https://github.com/BLAKE3-team/BLAKE3, BLAKE3} hash. Also as an
+    optimization, by default if file's @code{ctime} is same, then hash
+    check is skipped. Optionally you can disable that behaviour, or even
+    enable trust to file's @code{mtime}
 @item files creation is @code{umask}-friendly (unlike @code{mkstemp()}
     used in @command{redo-c})
 @item parallel build with jobs limit, optionally in infinite mode