Add some more details to the cargo fix --edition procedure.

Author: ehuss

src/doc/man/cargo-fix.md

@@ -44,9 +44,15 @@ or feature requests please don't hesitate to file an issue at
 The `cargo fix` subcommand can also be used to migrate a package from one
 [edition] to the next. The general procedure is:
 
-1. Run `cargo fix --edition`
+1. Run `cargo fix --edition`. Consider also using the `--all-features` flag if
+   your project has multiple features. You may also want to run `cargo fix
+   --edition` multiple times with different `--target` flags if your project
+   has platform-specific code gated by `cfg` attributes.
 2. Modify `Cargo.toml` to set the [edition field] to the new edition.
-3. Run your project tests to verify that everything still works.
+3. Run your project tests to verify that everything still works. If new
+   warnings are issued, you may want to consider running `cargo fix` again
+   (without the `--edition` flag) to apply any suggestions given by the
+   compiler.
 
 And hopefully that's it! Just keep in mind of the caveats mentioned above that
 `cargo fix` cannot update code for inactive features or `cfg` expressions.

src/doc/man/generated_txt/cargo-fix.txt

@@ -43,13 +43,19 @@ DESCRIPTION
        <https://doc.rust-lang.org/edition-guide/editions/transitioning-an-existing-project-to-a-new-edition.html>
        to the next. The general procedure is:
 
-       1. Run cargo fix --edition
+       1. Run cargo fix --edition. Consider also using the --all-features flag
+          if your project has multiple features. You may also want to run cargo
+          fix --edition multiple times with different --target flags if your
+          project has platform-specific code gated by cfg attributes.
 
        2. Modify Cargo.toml to set the edition field
           <https://doc.rust-lang.org/cargo/reference/manifest.html#the-edition-field>
           to the new edition.
 
-       3. Run your project tests to verify that everything still works.
+       3. Run your project tests to verify that everything still works. If new
+          warnings are issued, you may want to consider running cargo fix again
+          (without the --edition flag) to apply any suggestions given by the
+          compiler.
 
        And hopefully that's it! Just keep in mind of the caveats mentioned
        above that cargo fix cannot update code for inactive features or cfg

src/doc/src/commands/cargo-fix.md

@@ -44,9 +44,15 @@ or feature requests please don't hesitate to file an issue at
 The `cargo fix` subcommand can also be used to migrate a package from one
 [edition] to the next. The general procedure is:
 
-1. Run `cargo fix --edition`
+1. Run `cargo fix --edition`. Consider also using the `--all-features` flag if
+   your project has multiple features. You may also want to run `cargo fix
+   --edition` multiple times with different `--target` flags if your project
+   has platform-specific code gated by `cfg` attributes.
 2. Modify `Cargo.toml` to set the [edition field] to the new edition.
-3. Run your project tests to verify that everything still works.
+3. Run your project tests to verify that everything still works. If new
+   warnings are issued, you may want to consider running `cargo fix` again
+   (without the `--edition` flag) to apply any suggestions given by the
+   compiler.
 
 And hopefully that's it! Just keep in mind of the caveats mentioned above that
 `cargo fix` cannot update code for inactive features or `cfg` expressions.

src/etc/man/cargo-fix.1

@@ -52,15 +52,20 @@ The \fBcargo fix\fR subcommand can also be used to migrate a package from one
 \fIedition\fR <https://doc.rust\-lang.org/edition\-guide/editions/transitioning\-an\-existing\-project\-to\-a\-new\-edition.html> to the next. The general procedure is:
 .sp
 .RS 4
-\h'-04' 1.\h'+01'Run \fBcargo fix \-\-edition\fR
+\h'-04' 1.\h'+01'Run \fBcargo fix \-\-edition\fR\&. Consider also using the \fB\-\-all\-features\fR flag if
+your project has multiple features. You may also want to run \fBcargo fix \-\-edition\fR multiple times with different \fB\-\-target\fR flags if your project
+has platform\-specific code gated by \fBcfg\fR attributes.
 .RE
 .sp
 .RS 4
 \h'-04' 2.\h'+01'Modify \fBCargo.toml\fR to set the \fIedition field\fR <https://doc.rust\-lang.org/cargo/reference/manifest.html#the\-edition\-field> to the new edition.
 .RE
 .sp
 .RS 4
-\h'-04' 3.\h'+01'Run your project tests to verify that everything still works.
+\h'-04' 3.\h'+01'Run your project tests to verify that everything still works. If new
+warnings are issued, you may want to consider running \fBcargo fix\fR again
+(without the \fB\-\-edition\fR flag) to apply any suggestions given by the
+compiler.
 .RE
 .sp
 And hopefully that's it! Just keep in mind of the caveats mentioned above that