6200 - --dump is not needed for incremental traces

This undoes commit 5764, which was ill-considered. We already had incremental
prints at that point to 'last_run'. As long as we don't run out of RAM
on large traces, there doesn't seem any need to print to stderr.

Now '--dump' is only needed when juggling multiple traces.

1 files changed, 3 insertions, 7 deletions

diff --git a/001help.cc b/001help.cc
index de1b680f..5fd13a7b 100644
--- a/001help.cc
+++ b/001help.cc
@@ -81,13 +81,9 @@ void init_help() {
     "== Debugging aids\n"
     "- Add '--trace' to any of these commands to save a trace to disk at the end.\n"
     "  This can run out of memory for long-running commands.\n"
-    "- Add '--debug' to add information to traces. 'bootstrap --debug translate'\n"
-    "  will save metadata to disk that 'bootstrap --trace run' uses to make traces\n"
-    "  more informative.\n"
-    "- Add '--dump --trace' to emit a trace incrementally to stderr.\n"
-    "  This approach will work even for long-running programs.\n"
-    "  (Though the combination of flags is counter-intuitive and can probably\n"
-    "  be improved.)\n"
+    "- Add '--debug' to emit additional debug information during translation.\n"
+    "  'bootstrap --debug translate' will save metadata to disk that\n"
+    "  'bootstrap --trace run' uses to make traces more informative.\n"
     "\n"
     "Options starting with '--' must always come before any other arguments.\n"
     "\n"