Fix typos and adjust some documentation.
1.1 --- a/Makefile.in Tue Nov 17 09:54:10 2009 -0800
1.2 +++ b/Makefile.in Tue Nov 17 10:01:22 2009 -0800
1.3 @@ -129,7 +129,7 @@
1.4
1.5 # We create a script fragment that is parseable from inside a Makefile,
1.6 # but also from inside a shell script, hence the reason why we don't
1.7 -# use := to set varaibles, although that will incur a (very small)
1.8 +# use := to set variables, although that will incur a (very small)
1.9 # penalty from the Makefile that includes it (due to re-evaluation at
1.10 # each call).
1.11 paths.mk:
2.1 --- a/docs/overview.txt Tue Nov 17 09:54:10 2009 -0800
2.2 +++ b/docs/overview.txt Tue Nov 17 10:01:22 2009 -0800
2.3 @@ -366,22 +366,22 @@
2.4
2.5 If you want to stop the build after a step you are debugging, you can pass the
2.6 variable STOP to make:
2.7 - ct-ng STOP=some_step
2.8 + ct-ng build STOP=some_step
2.9
2.10 Conversely, if you want to restart a build at a specific step you are
2.11 debugging, you can pass the RESTART variable to make:
2.12 - ct-ng RESTART=some_step
2.13 + ct-ng build RESTART=some_step
2.14
2.15 Alternatively, you can call make with the name of a step to just do that step:
2.16 ct-ng libc_headers
2.17 is equivalent to:
2.18 - ct-ng RESTART=libc_headers STOP=libc_headers
2.19 + ct-ng build RESTART=libc_headers STOP=libc_headers
2.20
2.21 The shortcuts +step_name and step_name+ allow to respectively stop or restart
2.22 at that step. Thus:
2.23 - ct-ng +libc_headers and: ct-ng libc_headers+
2.24 + ct-ng +libc_headers and: ct-ng libc_headers+
2.25 are equivalent to:
2.26 - ct-ng STOP=libc_headers and: ct-ng RESTART=libc_headers
2.27 + ct-ng build STOP=libc_headers and: ct-ng build RESTART=libc_headers
2.28
2.29 To obtain the list of acceptable steps, please call:
2.30 ct-ng list-steps