@@ -441,7 +441,7 @@ impl Build {
441
441
// Cargo.toml files.
442
442
let rust_submodules = [ "library/backtrace" , "library/stdarch" ] ;
443
443
for s in rust_submodules {
444
- build. require_and_update_submodule (
444
+ build. require_submodule (
445
445
s,
446
446
Some (
447
447
"The submodule is required for the standard library \
@@ -482,7 +482,7 @@ impl Build {
482
482
///
483
483
/// This *does not* update the submodule if `config.toml` explicitly says
484
484
/// not to, or if we're not in a git repository (like a plain source
485
- /// tarball). Typically [`Build::require_and_update_submodule `] should be
485
+ /// tarball). Typically [`Build::require_submodule `] should be
486
486
/// used instead to provide a nice error to the user if the submodule is
487
487
/// missing.
488
488
fn update_submodule ( & self , relative_path : & str ) {
@@ -599,7 +599,7 @@ impl Build {
599
599
///
600
600
/// The given `err_hint` will be shown to the user if the submodule is not
601
601
/// checked out and submodule management is disabled.
602
- pub fn require_and_update_submodule ( & self , submodule : & str , err_hint : Option < & str > ) {
602
+ pub fn require_submodule ( & self , submodule : & str , err_hint : Option < & str > ) {
603
603
// When testing bootstrap itself, it is much faster to ignore
604
604
// submodules. Almost all Steps work fine without their submodules.
605
605
if cfg ! ( test) && !self . config . submodules ( ) {
@@ -628,7 +628,7 @@ impl Build {
628
628
/// management is disabled and the submodule does not exist.
629
629
pub fn require_and_update_all_submodules ( & self ) {
630
630
for submodule in build_helper:: util:: parse_gitmodules ( & self . src ) {
631
- self . require_and_update_submodule ( submodule, None ) ;
631
+ self . require_submodule ( submodule, None ) ;
632
632
}
633
633
}
634
634
0 commit comments