From 2c70b6abf4d9d78556125a145bdce1bbacbda5b4 Mon Sep 17 00:00:00 2001 From: Joshua Nelson Date: Sat, 23 Jul 2022 14:47:05 -0500 Subject: [PATCH] Don't give a hard error for `x check --keep-stage 0` Stage 1 check has been supported since https://github.com/rust-lang/rust/pull/81064. #81064 changed the error message for this, but I don't think there's any reason we should prevent using it. I tested locally and `keep-stage` works fine. Don't give a hard error when trying to use it. --- src/bootstrap/flags.rs | 9 --------- 1 file changed, 9 deletions(-) diff --git a/src/bootstrap/flags.rs b/src/bootstrap/flags.rs index 1822c2936b71f..80b3bcce86016 100644 --- a/src/bootstrap/flags.rs +++ b/src/bootstrap/flags.rs @@ -623,15 +623,6 @@ Arguments: } }; - if let Subcommand::Check { .. } = &cmd { - if matches.opt_str("keep-stage").is_some() - || matches.opt_str("keep-stage-std").is_some() - { - eprintln!("--keep-stage not yet supported for x.py check"); - crate::detail_exit(1); - } - } - Flags { verbose: matches.opt_count("verbose"), stage: matches.opt_str("stage").map(|j| j.parse().expect("`stage` should be a number")),