| Age | Commit message (Collapse) | Author | Lines |
|
|
|
We were using an alpha version before, pinned to a Git hash, so that we
could access a new feature (Michael-F-Bryan/mdbook-linkcheck#42).
Now there is a point release though (0.7.1), so we can update to that!
|
|
|
|
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
|
|
|
|
This makes the compiler faster to running without sacrificing too much
performance. It still shows logging so contributors aren't confused by
`debug!` doing nothing.
|
|
Co-authored-by: Camelid <camelidcamel@gmail.com>
|
|
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
|
|
|
|
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
|
|
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
|
|
|
|
|
|
|
|
|
|
Fixed two typos.
|
|
This is a companion to [this PR](https://github.com/rust-lang/rust/pull/76356), which deals with including functionality for automatically running `tidy --bless` on each commit.
Undo editor auto-formatting and clarify git hook renaming
a word
Phrasing
Apply suggestions from code review
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
|
|
|
|
|
|
* Explain stages in terms of the compiler currently running
- Address some confusing points
+ stage N+1 -> stage N artifacts
+ Use more likely examples of an ABI break
+ stage N -> stage N compiler
- Mention why rustc occasionally uses `cfg(bootstrap)`
- Note that stage1 is built using two different versions
- Add lots of examples
+ `test src/test/ui` and `test compiler/rustc` run different compilers 😢
+ Separate examples of what to do from examples of what not to do
- 'ship stage 1 artifacts' -> 'ship stage 2 compiler'
This is hopefully less confusing.
* build -> x.py build
* Add section on build artifacts
* Improve wording
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
* uplifted -> assembled
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
|
|
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
|
|
|
|
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
|
|
|
|
|
|
optimize, codegen-units and mir-opt do, but debug-assertions doesn't.
|
|
|
|
Implemented in https://github.com/rust-lang/rust/pull/76349
|
|
|
|
|
|
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
|
|
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
|
|
|
|
Also updated a few links that redirected.
|
|
|
|
`git merge-base master` does not work, you need
`git merge-base master HEAD` instead.
|
|
|
|
Co-authored-by: Yuki Okushi <huyuumi.dev@gmail.com>
|
|
|
|
I've run into lots of annoying failures from this.
- Make it runnable without arguments
- Add it in the README
|
|
|
|
The Advanced Rebasing section has been mostly rewritten to include
both a major suggestion from jyn and a general rewrite. Additional
thanks to camelid for some suggestions!
|
|
The previous iteration of the page was often wordy and
occasionally unclear. This has been cleaned up in places.
Additionally, the TODO in the no-merge policy section has been
removed and addressed.
|
|
This section addresses the biggest issues that new contributors,
especially those with limited familiarity with git, are likely to
face. This is still a WIP.
Thanks to jyn for the recommended improvements!
|
|
|
|
(As suggested by jyn514.)
|
|
Reduced line length to <100 (as indicated by PR build error).
(Also removed extra space character before link.)
|
|
Linking directly to the relevant/example document source locations makes it easier for potential contributors to find them.
|
|
|
|
A link to the relevant section of the contributing documentation makes it easier for contributors to locate the relevant information. (e.g. via an in-page search for "doc".)
This is particularly important currently as https://github.com/rust-lang/rust/blob/85072e330394440776ace5ae612e3ced32ef6348/CONTRIBUTING.md links directly to the (currently `rustc`-focused) "Getting Started" guide rather than the general Rust contribution content to which it used to point.
|