mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Rollup merge of #142413 - tshepang:rdg-push, r=jieyouxu 

rustc-dev-guide subtree update

r? `@ghost`
This commit is contained in:
Matthias Krüger 2025-06-13 05:17:00 +02:00 committed by GitHub
parent 0380de71ac 6966390e79
commit 8b05b4dfe3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
rust-version
View File

@ -1 +1 @@
c31cccb7b5cc098b1a8c1794ed38d7fdbec0ccb0 14346303d760027e53214e705109a62c0f00b214

3
src/git.md
View File

@ -142,7 +142,8 @@ The most common cause is that you rebased after a change and ran `git add .` wit
`x` to update the submodules. Alternatively, you might have run `cargo fmt` instead of `x fmt` `x` to update the submodules. Alternatively, you might have run `cargo fmt` instead of `x fmt`
and modified files in a submodule, then committed the changes. and modified files in a submodule, then committed the changes.
To fix it, do the following things: To fix it, do the following things (if you changed a submodule other than cargo,
replace `src/tools/cargo` with the path to that submodule):
1. See which commit has the accidental changes: `git log --stat -n1 src/tools/cargo` 1. See which commit has the accidental changes: `git log --stat -n1 src/tools/cargo`
2. Revert the changes to that commit: `git checkout <my-commit>~ src/tools/cargo`. Type `~` 2. Revert the changes to that commit: `git checkout <my-commit>~ src/tools/cargo`. Type `~`

2
src/tests/compiletest.md
View File

@ -115,7 +115,7 @@ default behavior without any commands is to:
2. Run `rustc -Zunpretty=normal` on the output of the previous step. 2. Run `rustc -Zunpretty=normal` on the output of the previous step.
3. The output of the previous two steps should be the same. 3. The output of the previous two steps should be the same.
4. Run `rustc -Zno-codegen` on the output to make sure that it can type check 4. Run `rustc -Zno-codegen` on the output to make sure that it can type check
(this is similar to running `cargo check`). (similar to `cargo check`).
If any of the commands above fail, then the test fails. If any of the commands above fail, then the test fails.