X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fcmds.texi;h=465ef65f424406adb1a30bf61542ed0600f288d3;hb=2cea0c64b5a0240bfe6746a98a5b350812edb96d;hp=4c396093c4651ab969f1965fa90ccb8cfce0f10a;hpb=2e85fe511f4f0410e4b8a1dcdb127396b7f3f7c0;p=goredo.git

diff --git a/doc/cmds.texi b/doc/cmds.texi
index 4c39609..465ef65 100644
--- a/doc/cmds.texi
+++ b/doc/cmds.texi
@@ -31,14 +31,7 @@ With @option{-j} option you can enable parallel builds, probably with an
 infinite number of workers (@code{=0}). Also you can set
 @env{$REDO_JOBS} to automatically apply that setting globally.
 
-With @option{-k} (@env{$REDO_LOGS=1}) option you can capture job's
-@code{stderr} on the disk and read it later with @command{redo-log}
-command. Log's lines have @url{http://cr.yp.to/libtai/tai64.html,
-TAI64N} timestamp. You can decode it with @command{tai64nlocal} utility
-from @url{http://cr.yp.to/daemontools.html, daemontools}, or similar
-one: @code{go get go.cypherpunks.ru/tai64n/cmd/tai64nlocal}.
-@option{-s} (@env{$REDO_SILENT=1}) omits @code{stderr} printing at
-all, but you can still capture it with @option{-k}.
+Read about @ref{Logs, log storage capabilities}.
 
 @option{-log-pid} (@env{$REDO_LOG_PID=1}) can be used to prefix job's
 @code{stderr} with the PID, that could be useful during parallel builds.
@@ -53,12 +46,6 @@ By default all build commands use @code{fsync} to assure data is reached
 the disk. You can disable its usage with @env{$REDO_NO_SYNC=1}
 environment variable, for speeding up the build process.
 
-@command{goredo} determines target is out-of-date by comparing its size,
-@code{ctime} and content's hash, if @code{ctime} differs. Depending on
-the filesystem you use, probably you can not trust its @code{ctime}
-value at all. In that case you can set @env{$REDO_INODE_NO_TRUST=1} to
-forcefully verify the hash.
-
 There are other commands that could be found in other implementations too:
 
 @table @command