No .rec required for recursive logs

[goredo.git] / doc / news.texi

diff --git a/doc/news.texi b/doc/news.texi
index 3574f79515eb9bf01d50e37a92959fe19c49dc5d..c280785c633c213eda865156603e72d89bc75cc4 100644 (file)
--- a/doc/news.texi
+++ b/doc/news.texi
@@ -1,11 +1,20 @@
 @node News
 @unnumbered News
 
+@anchor{Release 1_10_0}
+@section Release 1.10.0
+@itemize
+@item
+    @command{redo-cleanup} now also cleans @file{.redo/tgt.log.rec} files.
+@item
+    Recursive logs do not require @file{.redo/tgt.rec} existence anymore.
+@end itemize
+
 @anchor{Release 1_9_0}
 @section Release 1.9.0
 @itemize
 @item
-    Do not enable command lines options not applicable to the command.
+    Do not enable command line options not applicable to the command.
     For example @option{-j} option is only applicable to @command{redo}
     and @command{redo-ifchange} commands.
 @item
@@ -14,6 +23,16 @@
     @item @option{-logs} option is renamed to @option{-k}
     @item @option{-silent} option is renamed to @option{-s}
     @end itemize
+@item
+    When @code{stderr} logs are kept, all environment variables, working
+    directory, command line arguments, start/finish times, duration,
+    participated PIDs, return codes are saved in corresponding
+    @file{.redo/tgt.log.rec} file. Some of them can be viewed with
+    @option{-c} option to @command{redo-log}.
+@item
+    @command{redo-log}'s @option{-r} option allows recursive, indented
+    viewing of the whole redo commands invocations for the given target
+    in serialized way.
 @end itemize
 
 @anchor{Release 1_8_0}