From 65a9bbce707c39b2487319c0ed7f9f16b89f3065 Mon Sep 17 00:00:00 2001 From: onur-ozkan Date: Sun, 7 Jul 2024 00:15:24 +0300 Subject: [PATCH] use "bootstrap" instead of "rustbuild" Let's stick with the single name "bootstrap" to refer to the bootstrap project to avoid confusion. Signed-off-by: onur-ozkan --- src/building/how-to-build-and-run.md | 2 +- src/rustdoc.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/building/how-to-build-and-run.md b/src/building/how-to-build-and-run.md index 336135978..c6b8bdc9f 100644 --- a/src/building/how-to-build-and-run.md +++ b/src/building/how-to-build-and-run.md @@ -356,7 +356,7 @@ in other sections: ### Cleaning out build directories Sometimes you need to start fresh, but this is normally not the case. -If you need to run this then `rustbuild` is most likely not acting right and +If you need to run this then bootstrap is most likely not acting right and you should file a bug as to what is going wrong. If you do need to clean everything up then you only need to run one command! diff --git a/src/rustdoc.md b/src/rustdoc.md index 02da8be81..dbaf0c0bf 100644 --- a/src/rustdoc.md +++ b/src/rustdoc.md @@ -75,7 +75,7 @@ does is call the `main()` that's in this crate's `lib.rs`, though.) * The Markdown renderer is loaded up in `html/markdown.rs`, including functions for extracting doctests from a given block of Markdown. * The tests on the structure of rustdoc HTML output are located in `tests/rustdoc`, where - they're handled by the test runner of rustbuild and the supplementary script + they're handled by the test runner of bootstrap and the supplementary script `src/etc/htmldocck.py`. ## Tests