Update docs for default absent authors field

Author: lf-

src/doc/man/cargo-init.md

@@ -20,8 +20,6 @@ will be used. If not, then a sample `src/main.rs` file will be created, or
 If the directory is not already in a VCS repository, then a new repository
 is created (see `--vcs` below).
 
-{{> description-new-authors }}
-
 See {{man "cargo-new" 1}} for a similar command which will create a new package in
 a new directory.
 

src/doc/man/cargo-new.md

@@ -15,8 +15,6 @@ includes a simple template with a `Cargo.toml` manifest, sample source file,
 and a VCS ignore file. If the directory is not already in a VCS repository,
 then a new repository is created (see `--vcs` below).
 
-{{> description-new-authors }}
-
 See {{man "cargo-init" 1}} for a similar command which will create a new manifest
 in an existing directory.
 

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

@@ -17,44 +17,6 @@ DESCRIPTION
        If the directory is not already in a VCS repository, then a new
        repository is created (see --vcs below).
 
-       The "authors" field in the manifest is determined from the environment
-       or configuration settings. A name is required and is determined from
-       (first match wins):
-
-       o  cargo-new.name Cargo config value
-
-       o  CARGO_NAME environment variable
-
-       o  GIT_AUTHOR_NAME environment variable
-
-       o  GIT_COMMITTER_NAME environment variable
-
-       o  user.name git configuration value
-
-       o  USER environment variable
-
-       o  USERNAME environment variable
-
-       o  NAME environment variable
-
-       The email address is optional and is determined from:
-
-       o  cargo-new.email Cargo config value
-
-       o  CARGO_EMAIL environment variable
-
-       o  GIT_AUTHOR_EMAIL environment variable
-
-       o  GIT_COMMITTER_EMAIL environment variable
-
-       o  user.email git configuration value
-
-       o  EMAIL environment variable
-
-       See the reference
-       <https://doc.rust-lang.org/cargo/reference/config.html> for more
-       information about configuration files.
-
        See cargo-new(1) for a similar command which will create a new package
        in a new directory.
 

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

@@ -12,44 +12,6 @@ DESCRIPTION
        source file, and a VCS ignore file. If the directory is not already in a
        VCS repository, then a new repository is created (see --vcs below).
 
-       The "authors" field in the manifest is determined from the environment
-       or configuration settings. A name is required and is determined from
-       (first match wins):
-
-       o  cargo-new.name Cargo config value
-
-       o  CARGO_NAME environment variable
-
-       o  GIT_AUTHOR_NAME environment variable
-
-       o  GIT_COMMITTER_NAME environment variable
-
-       o  user.name git configuration value
-
-       o  USER environment variable
-
-       o  USERNAME environment variable
-
-       o  NAME environment variable
-
-       The email address is optional and is determined from:
-
-       o  cargo-new.email Cargo config value
-
-       o  CARGO_EMAIL environment variable
-
-       o  GIT_AUTHOR_EMAIL environment variable
-
-       o  GIT_COMMITTER_EMAIL environment variable
-
-       o  user.email git configuration value
-
-       o  EMAIL environment variable
-
-       See the reference
-       <https://doc.rust-lang.org/cargo/reference/config.html> for more
-       information about configuration files.
-
        See cargo-init(1) for a similar command which will create a new manifest
        in an existing directory.
 

src/doc/man/includes/description-new-authors.md

@@ -20,32 +20,6 @@ will be used. If not, then a sample `src/main.rs` file will be created, or
 If the directory is not already in a VCS repository, then a new repository
 is created (see `--vcs` below).
 
-The "authors" field in the manifest is determined from the environment or
-configuration settings. A name is required and is determined from (first match
-wins):
-
-- `cargo-new.name` Cargo config value
-- `CARGO_NAME` environment variable
-- `GIT_AUTHOR_NAME` environment variable
-- `GIT_COMMITTER_NAME` environment variable
-- `user.name` git configuration value
-- `USER` environment variable
-- `USERNAME` environment variable
-- `NAME` environment variable
-
-The email address is optional and is determined from:
-
-- `cargo-new.email` Cargo config value
-- `CARGO_EMAIL` environment variable
-- `GIT_AUTHOR_EMAIL` environment variable
-- `GIT_COMMITTER_EMAIL` environment variable
-- `user.email` git configuration value
-- `EMAIL` environment variable
-
-See [the reference](../reference/config.html) for more information about
-configuration files.
-
-
 See [cargo-new(1)](cargo-new.html) for a similar command which will create a new package in
 a new directory.
 

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

@@ -15,32 +15,6 @@ includes a simple template with a `Cargo.toml` manifest, sample source file,
 and a VCS ignore file. If the directory is not already in a VCS repository,
 then a new repository is created (see `--vcs` below).
 
-The "authors" field in the manifest is determined from the environment or
-configuration settings. A name is required and is determined from (first match
-wins):
-
-- `cargo-new.name` Cargo config value
-- `CARGO_NAME` environment variable
-- `GIT_AUTHOR_NAME` environment variable
-- `GIT_COMMITTER_NAME` environment variable
-- `user.name` git configuration value
-- `USER` environment variable
-- `USERNAME` environment variable
-- `NAME` environment variable
-
-The email address is optional and is determined from:
-
-- `cargo-new.email` Cargo config value
-- `CARGO_EMAIL` environment variable
-- `GIT_AUTHOR_EMAIL` environment variable
-- `GIT_COMMITTER_EMAIL` environment variable
-- `user.email` git configuration value
-- `EMAIL` environment variable
-
-See [the reference](../reference/config.html) for more information about
-configuration files.
-
-
 See [cargo-init(1)](cargo-init.html) for a similar command which will create a new manifest
 in an existing directory.
 

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

@@ -33,7 +33,6 @@ This is all we need to get started. First, let’s check out `Cargo.toml`:
 [package]
 name = "hello_world"
 version = "0.1.0"
-authors = ["Your Name <[email protected]>"]
 edition = "2018"
 
 [dependencies]

src/doc/src/getting-started/first-steps.md

@@ -68,8 +68,6 @@ dep-info-basedir = "…"        # path for the base directory for targets in dep
 pipelining = true             # rustc pipelining
 
 [cargo-new]
-name = "Your Name"        # name to use in `authors` field
-email = "[email protected]" # email address to use in `authors` field
 vcs = "none"              # VCS to use ('git', 'hg', 'pijul', 'fossil', 'none')
 
 [http]
@@ -401,27 +399,6 @@ schedule overlapping invocations of `rustc` in parallel when possible.
 
 The `[cargo-new]` table defines defaults for the [`cargo new`] command.
 
-##### `cargo-new.name`
-* Type: string
-* Default: from environment
-* Environment: `CARGO_NAME` or `CARGO_CARGO_NEW_NAME`
-
-Defines the name to use in the `authors` field when creating a new
-`Cargo.toml` file. If not specified in the config, Cargo searches the
-environment or your `git` configuration as described in the [`cargo new`]
-documentation.
-
-##### `cargo-new.email`
-* Type: string
-* Default: from environment
-* Environment: `CARGO_EMAIL` or `CARGO_CARGO_NEW_EMAIL`
-
-Defines the email address used in the `authors` field when creating a new
-`Cargo.toml` file. If not specified in the config, Cargo searches the
-environment or your `git` configuration as described in the [`cargo new`]
-documentation. The `email` value may be set to an empty string to prevent
-Cargo from placing an address in the authors field.
-
 ##### `cargo-new.vcs`
 * Type: string
 * Default: "git" or "none"

src/doc/src/reference/config.md

@@ -34,7 +34,6 @@ Check out the [metadata you can specify](manifest.md) in `Cargo.toml` to
 ensure your crate can be discovered more easily! Before publishing, make sure
 you have filled out the following fields:
 
-- [`authors`]
 - [`license` or `license-file`]
 - [`description`]
 - [`homepage`]