@node Logs
+@cindex logging
@unnumbered Logs
+@vindex REDO_LOGS
+@vindex REDO_SILENT
@code{stderr} of the running targets can be kept on the disk by
specifying @option{-k} option (or by setting @env{$REDO_LOGS=1}
environment variable) to @command{redo}. You can simultaneously
$ redo -xx -k -s build-the-whole-huge-project
@end example
+@cindex TAI64
+@cindex TAI64N
+@pindex tai64nlocal
Logs are stored in corresponding @file{.redo/tgt.log} file. Each line of
it is prefixed with @url{http://cr.yp.to/libtai/tai64.html, TAI64N}
timestamp, that you can decode with @command{tai64nlocal} utility from
@option{-s}ilence was enabled) is printed as it appears, mixing output
from all commands, that is hard to read and investigate. Serialized
@command{redo-log} output rearranges output. I will take example from
-original apenwarr's idea @url{https://apenwarr.ca/log/20181106,
-article}. Serialized output will look like this:
+original apenwarr's idea @url{https://apenwarr.ca/log/20181106, article}.
+Serialized output will look like this:
@verbatim
$ redo-log -r A