squiid/rust
1
0
Fork 0
Code Issues Pull requests Projects Activity

Bump rustfmt and stage0

Browse source
This commit is contained in:
Mark Rousskov 2020-01-31 12:25:38 -05:00
parent b613b0cb36
commit ff95473b5e
2 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/bootstrap/channel.rs
View file

@ -13,7 +13,7 @@ use build_helper::output;
use crate::Build; use crate::Build;
// The version number // The version number
pub const CFG_RELEASE_NUM: &str = "1.42.0"; pub const CFG_RELEASE_NUM: &str = "1.43.0";
pub struct GitInfo { pub struct GitInfo {
inner: Option<Info>, inner: Option<Info>,

11
src/stage0.txt
View file

@ -12,14 +12,15 @@
# source tarball for a stable release you'll likely see `1.x.0` for rustc and # source tarball for a stable release you'll likely see `1.x.0` for rustc and
# `0.x.0` for Cargo where they were released on `date`. # `0.x.0` for Cargo where they were released on `date`.
date: 2019-12-18 date: 2020-01-30
rustc: beta rustc: beta
cargo: beta cargo: beta
# We use a nightly rustfmt to format the source because it solves some bootstrapping # We use a nightly rustfmt to format the source because it solves some
# issues with use of new syntax in this repo. If you're looking at the beta/stable branch, this key should be omitted, # bootstrapping issues with use of new syntax in this repo. If you're looking at
# as we don't want to depend on rustfmt from nightly there. # the beta/stable branch, this key should be omitted, as we don't want to depend
rustfmt: nightly-2019-12-18 # on rustfmt from nightly there.
rustfmt: nightly-2020-01-31
# When making a stable release the process currently looks like: # When making a stable release the process currently looks like:
# #