about summary refs log tree commit diff
path: root/tests
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-03-17 15:51:28 +0000
committerbors <bors@rust-lang.org>2025-03-17 15:51:28 +0000
commit8279176ccdfd4eebd40a671f75b6d3024ae56b42 (patch)
tree9211ac589843f4f8040e0310a6a15347e7ffcebf /tests
parent9c67cecd12d79f1bbc00a74f70e7ef9fff086a5a (diff)
parent4579615b14a3a2ee1a0040365d969d9526ed7e1c (diff)
downloadrust-8279176ccdfd4eebd40a671f75b6d3024ae56b42.tar.gz
rust-8279176ccdfd4eebd40a671f75b6d3024ae56b42.zip
Auto merge of #137081 - Shourya742:2025-02-15-change-config.toml-to-bootstrap.toml, r=onur-ozkan,jieyouxu,kobzol
change config.toml to bootstrap.toml

Currently, both Bootstrap and Cargo uses same name as their configuration file, which can be confusing. This PR is based on a discussion to rename `config.toml` to `bootstrap.toml` for Bootstrap. Closes: https://github.com/rust-lang/rust/issues/126875.

I have split the PR into atomic commits to make it easier to review. Once the changes are finalized, I will squash them. I am particularly concerned about the changes made to modules that are not part of Bootstrap. How should we handle those changes? Should we ping the respective maintainers?
Diffstat (limited to 'tests')
-rw-r--r--tests/run-make/linker-warning/rmake.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/run-make/linker-warning/rmake.rs b/tests/run-make/linker-warning/rmake.rs
index 73ad248b6f3..bc21739fefc 100644
--- a/tests/run-make/linker-warning/rmake.rs
+++ b/tests/run-make/linker-warning/rmake.rs
@@ -4,7 +4,7 @@ fn run_rustc() -> Rustc {
     let mut rustc = rustc();
     rustc
         .arg("main.rs")
-        // NOTE: `link-self-contained` can vary depending on config.toml.
+        // NOTE: `link-self-contained` can vary depending on bootstrap.toml.
         // Make sure we use a consistent value.
         .arg("-Clink-self-contained=-linker")
         .arg("-Zunstable-options")