@@ -178,14 +178,14 @@ and a populated cache of the crates reflected in the lock file. If either of
178
178
these components are missing, then they're required for the build to succeed and
179
179
must be fetched remotely.
180
180
181
- As of Rust 1.11.0 (to be released 2016-09-29) Cargo understands a new flag,
182
- ` --frozen ` , which is an assertion that it shouldn't touch the network. When
183
- passed, Cargo will immediately return an error if it would otherwise attempt a
184
- network request. The error should include contextual information about why the
185
- network request is being made in the first place to help debug as well. Note
186
- that this flag * does not change the behavior of Cargo* , it simply asserts that
187
- Cargo shouldn't touch the network as a previous command has been run to ensure
188
- that network activity shouldn't be necessary.
181
+ As of Rust 1.11.0 Cargo understands a new flag, ` --frozen ` , which is an
182
+ assertion that it shouldn't touch the network. When passed, Cargo will
183
+ immediately return an error if it would otherwise attempt a network request.
184
+ The error should include contextual information about why the network request is
185
+ being made in the first place to help debug as well. Note that this flag * does
186
+ not change the behavior of Cargo* , it simply asserts that Cargo shouldn't touch
187
+ the network as a previous command has been run to ensure that network activity
188
+ shouldn't be necessary.
189
189
190
190
For more information about vendoring, see documentation on [ source
191
191
replacement] [ replace ] .
0 commit comments