X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fnews.texi;h=4f5ab5b437009779190e60a6f99812feeb676509;hb=bf96757828d2ae663f5f54147c0e229f74fc9357;hp=3574f79515eb9bf01d50e37a92959fe19c49dc5d;hpb=3fa21c8c7e74798a07fbcc99030bae7c2505f76d;p=goredo.git

diff --git a/doc/news.texi b/doc/news.texi
index 3574f79..4f5ab5b 100644
--- a/doc/news.texi
+++ b/doc/news.texi
@@ -1,11 +1,93 @@
 @node News
 @unnumbered News
 
+@anchor{Release 1_19_0}
+@section Release 1.19.0
+@itemize
+@item
+    Skip target itself, when searching for corresponding @file{.do}
+    file. For example @file{default.do} must use @file{../default.do}
+    instead of the self.
+@end itemize
+
+@anchor{Release 1_18_0}
+@section Release 1.18.0
+@itemize
+@item
+    Fix regression of known OODs passing since 1.3.0, that leads to
+    rebuilding of already built targets.
+@end itemize
+
+@anchor{Release 1_17_0}
+@section Release 1.17.0
+@itemize
+@item
+    If @command{redo*} process is killed, then it sends @code{SIGTERM}
+    to all his children too, properly terminating the whole job queue.
+@end itemize
+
+@anchor{Release 1_16_0}
+@section Release 1.16.0
+@itemize
+@item
+    Unexistent targets are considered always out-of-date, as it should be.
+@item
+    Do not panic if @env{$REDO_LOGS=1} and we were unable to start the command.
+@end itemize
+
+@anchor{Release 1_15_0}
+@section Release 1.15.0
+@itemize
+@item
+    Explicitly check if @code{$1} target is touched and then fail.
+    Previously we check if @code{$1} was only altered.
+@end itemize
+
+@anchor{Release 1_14_0}
+@section Release 1.14.0
+@itemize
+@item
+    Fixed @command{redo-ifcreate}'s targets proper relative paths to the target.
+@end itemize
+
+@anchor{Release 1_13_0}
+@section Release 1.13.0
+@itemize
+@item
+    Use @file{.log-rec} extension, instead of @file{.log.rec}, that
+    won't collide with already existing @file{.log} and @file{.rec} in
+    @file{.redo} directory.
+@end itemize
+
+@anchor{Release 1_12_0}
+@section Release 1.12.0
+@itemize
+@item
+    Fix possible lack of success finish message printing if any of
+    targets fail.
+@end itemize
+
+@anchor{Release 1_11_0}
+@section Release 1.11.0
+@itemize
+@item
+    Fix nasty bug with incorrect @file{.redo/tgt.rec} files renaming.
+@end itemize
+
+@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 +96,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}