"in tree" should be "in-tree"

This commit is contained in:
Tshepang Mbambo 2026-01-12 20:14:36 +02:00
parent 52a5023e76
commit 2204cbd987
2 changed files with 6 additions and 6 deletions

View file

@ -29,7 +29,7 @@ The following external projects are managed using some form of a `subtree`:
In contrast to `submodule` dependencies
(see below for those), the `subtree` dependencies are just regular files and directories which can
be updated in tree. However, if possible, enhancements, bug fixes, etc. specific
be updated in-tree. However, if possible, enhancements, bug fixes, etc. specific
to these tools should be filed against the tools directly in their respective upstream repositories.
The exception is that when rustc changes are required to
implement a new tool feature or test, that should happen in one collective rustc PR.

View file

@ -130,7 +130,7 @@ means the test won't be compiled or run.
main test files but that `compiletest` should not try to build the file itself.
Please backlink to which main test is actually using the auxiliary file.
* `ignore-test` always ignores the test. This can be used to temporarily disable
a test if it is currently not working, but you want to keep it in tree to
a test if it is currently not working, but you want to keep it in-tree to
re-enable it later.
Some examples of `X` in `ignore-X` or `only-X`:
@ -211,7 +211,7 @@ settings:
- `needs-target-std` — ignores if target platform does not have std support.
- `ignore-backends` — ignores the listed backends, separated by whitespace characters. Please note
that this directive can be overriden with the `--bypass-ignore-backends=[BACKEND]` command line
flag.
flag.
- `needs-backends` — only runs the test if current codegen backend is listed.
- `needs-offload` — ignores if our LLVM backend was not built with offload support.
- `needs-enzyme` — ignores if our Enzyme submodule was not built.
@ -290,9 +290,9 @@ You can also force `./x test` to use a specific edition by passing the `-- --edi
However, tests with the `//@ edition` directive will clamp the value passed to the argument.
For example, if we run `./x test -- --edition=2015`:
- A test with the `//@ edition: 2018` will run with the 2018 edition.
- A test with the `//@ edition: 2015..2021` will be run with the 2015 edition.
- A test with the `//@ edition: 2018..` will run with the 2018 edition.
- A test with the `//@ edition: 2018` will run with the 2018 edition.
- A test with the `//@ edition: 2015..2021` will be run with the 2015 edition.
- A test with the `//@ edition: 2018..` will run with the 2018 edition.
### Rustdoc