Remove regtest actions, introduce build-all actions:

- regtest was not easy to use
- one may wish to simply build all samples
- introduce a per-sample automatic build

 /trunk/docs/overview.txt  |   19    14     5     0 ++++++++---
 /trunk/samples/samples.mk |   92    49    43     0 ++++++++++++++++++++++++++++-------------------------
 /trunk/ct-ng.comp         |    8     5     3     0 +++--
 3 files changed, 68 insertions(+), 51 deletions(-)

1 files changed, 14 insertions, 5 deletions

diff --git a/docs/overview.txt b/docs/overview.txt
index c040646..743592c 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -336,11 +336,11 @@ Note that in order to restart a build, you'll have to say 'Y' to the config
 option CT_DEBUG_CT_SAVE_STEPS, and that the previous build effectively went
 that far.
 
-Testing all toolchains at once |
--------------------------------+
+Building all toolchains at once |
+--------------------------------+
 
-You can test-build all samples; simply call:
-  ct-ng regtest
+You can build all samples; simply call:
+  ct-ng build-all
 
 Overriding the number of // jobs |
 ---------------------------------+
@@ -354,7 +354,16 @@ which tells crosstool-NG to override the number of // jobs to 4.
 
 You can see the actions that support overriding the number of // jobs in
 the help menu. Those are the ones with [.#] after them (eg. build[.#] or
-regtest[.#], and so on...).
+build-all[.#], and so on...).
+
+Note on // jobs |
+----------------+
+
+The crosstool-NG script 'ct-ng' is a Makefile-script. It does *not* execute
+in parallel (there is not much to gain). When speaking of // jobs, we are
+refering to the number of // jobs when making the *components*. That is, we
+speak of the number of // jobs used to build gcc, glibc, and so on...
+
 
 _______________________
                       /