X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fnews.texi;h=088cc03a77955564e3ae881be21abebf7e7fcd6e;hb=3c87984511180d7bf865574123195588ea8c044c;hp=c280785c633c213eda865156603e72d89bc75cc4;hpb=46e189a9c6398c1ab1245ab1e9827b959db29219;p=goredo.git

diff --git a/doc/news.texi b/doc/news.texi
index c280785..088cc03 100644
--- a/doc/news.texi
+++ b/doc/news.texi
@@ -1,6 +1,132 @@
 @node News
+@cindex news
 @unnumbered News
 
+@anchor{Release 1_23_0}
+@section Release 1.23.0
+@itemize
+@item
+    @command{redo-ifchange}'s @option{-f} option forces each target
+    rebuilding. Comparing to @command{redo}, it will parallelize the
+    process.
+@item
+    Inode's number is also stored as dependency information, just to
+    prevent possible @code{ctime} collision of two files.
+@item
+    Performance optimization: do not use target's temporary output file
+    at all, if its hash equals to already existing target's one. Just
+    touch existing target file instead.
+@end itemize
+
+@anchor{Release 1_22_0}
+@section Release 1.22.0
+@itemize
+@item
+    @code{flock} locks replaced with POSIX @code{fcntl} ones.
+    They could be more portable.
+@item
+    @command{redo-depfix} command appeared, that traverses through all
+    @file{.redo} directories and their dependency files, checks if
+    corresponding targets has the same content but different
+    @code{ctime}/@code{mtime} values and rewrites dependencies with that
+    updated inode information.
+@item
+    With @env{$REDO_STOP_IF_MODIFIED=1} environment variable redo will
+    stop and fail if it meet externally modified file. By default user
+    is only warned about it, but building continues for convenience.
+@end itemize
+
+@anchor{Release 1_21_0}
+@section Release 1.21.0
+@itemize
+@item
+    @env{$REDO_INODE_NO_TRUST} is replaced with @env{$REDO_INODE_TRUST}
+    environment variable, that takes either @code{none}, or @code{ctime}
+    (the default one), or @code{mtime} (new one). Check documentation's
+    separate page about that option.
+@end itemize
+
+@anchor{Release 1_20_0}
+@section Release 1.20.0
+@itemize
+@item
+    Print warning message if both ifcreate and ifchange records were
+    discovered after the target is done.
+@end itemize
+
+@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