about summary refs log tree commit diff
diff options
context:
space:
mode:
authorChristian Neukirchen <chneukirchen@gmail.com>2015-09-06 21:13:07 +0200
committerChristian Neukirchen <chneukirchen@gmail.com>2015-09-06 21:13:07 +0200
commite4140ae6022f380aa14d3682455bdfce8c698bda (patch)
treeb21b83d666eef151ae7ed60e28aa3214bf15ca4c
parent467d98065f9076b2f63423dba1d9fafd1c5b8ee1 (diff)
downloadredo-c-e4140ae6022f380aa14d3682455bdfce8c698bda.tar.gz
redo-c-e4140ae6022f380aa14d3682455bdfce8c698bda.tar.xz
redo-c-e4140ae6022f380aa14d3682455bdfce8c698bda.zip
Mention redo -f / redo -k
-rw-r--r--NOTES8
1 files changed, 6 insertions, 2 deletions
diff --git a/NOTES b/NOTES
index 0df7a6b..383acf6 100644
--- a/NOTES
+++ b/NOTES
@@ -20,8 +20,8 @@
 
 * `default.do` files are checked in all parent directories up to `/`.
 
-* Parallel builds can be started with `redo -j N`, this uses a job
-  broker similar to but not compatible with GNU make.
+* Parallel builds can be started with `redo -j N` (or `JOBS=N redo`),
+  this uses a job broker similar to but not compatible with GNU make.
 
 * To detect whether a file has changed, we first compare `ctime` and
   in case it differs, a SHA2 hash of the contents.
@@ -30,3 +30,7 @@
   This is an implementation detail.
 
 * Builds can be started from every directory and should yield same results.
+
+* `redo -f` will consider all targets outdated and force a rebuild.
+
+* `redo -k` will keep going if a target failed to build.