@node News
+@cindex news
@unnumbered News
+@anchor{Release 1_24_0}
+@section Release 1.24.0
+@itemize
+@item
+ @command{redo-cleanup tmp} also removes temporarily (@code{$3})
+ created directories.
+@end itemize
+
+@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