@node News
@unnumbered News
+@anchor{Release 1.8.0}
+@section Release 1.8.0
+@itemize
+@item
+ Fixed possibly wrong relative path record of the dependency, when
+ redo commands are run in different directory from the @file{.do}.
+@item
+ Fixed possible failing in @command{redo-sources} if no @file{.dep}
+ is found.
+@end itemize
+
+@anchor{Release 1.7.0}
+@section Release 1.7.0
+@itemize
+@item
+ Optional compatibility (through @env{REDO_MAKE=@{bmake|gmake@}})
+ with either NetBSD's bmake or GNU Make jobserver protocols, being
+ able to tightly integrate @command{goredo} with the @command{make}.
+@end itemize
+
+@anchor{Release 1.6.0}
+@section Release 1.6.0
+@itemize
+@item
+ @command{redo-affects} command appeared, that shows all targets that
+ will be affected by changing the specified ones.
+@end itemize
+
+@anchor{Release 1.5.0}
+@section Release 1.5.0
+@itemize
+@item
+ @command{redo-ood}, @command{redo-sources} and
+ @command{redo-targets} can optionally take list of targets to apply
+ the command on, to narrow the result.
+@item
+ @command{redo-sources} mistakenly missed @file{.do} files in the output.
+@item
+ @command{redo-sources} now recursively searches for all source
+ files, not the "first" depth level ones.
+@end itemize
+
@anchor{Release 1.4.1}
@section Release 1.4.1
@itemize