Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
- 2.18.1 → 2.30.0 no changes
- 2.18.0 06/21/18
For each “Name <user@host>” or “<user@host>” from the command-line
or standard input (when using
--stdin), look up the person’s canonical name
and email address (see "Mapping Authors" below). If found, print them;
otherwise print the input as-is.
For each contact, a single line is output, terminated by a newline. If the name is provided or known to the mailmap, “Name <user@host>” is printed; otherwise only “<user@host>” is printed.
If the file
.mailmap exists at the toplevel of the repository, or at
the location pointed to by the mailmap.file or mailmap.blob
configuration options, it
is used to map author and committer names and email addresses to
canonical real names and email addresses.
In the simple form, each line in the file consists of the canonical real name of an author, whitespace, and an email address used in the commit (enclosed by < and >) to map to the name. For example:
Proper Name <email@example.com>
The more complex forms are:
which allows mailmap to replace only the email part of a commit, and:
Proper Name <firstname.lastname@example.org> <email@example.com>
which allows mailmap to replace both the name and the email of a commit matching the specified commit email address, and:
Proper Name <firstname.lastname@example.org> Commit Name <email@example.com>
which allows mailmap to replace both the name and the email of a commit matching both the specified commit name and email address.
Example 1: Your history contains commits by two authors, Jane and Joe, whose names appear in the repository under several forms:
Joe Developer <firstname.lastname@example.org> Joe R. Developer <email@example.com> Jane Doe <firstname.lastname@example.org> Jane Doe <jane@laptop.(none)> Jane D. <jane@desktop.(none)>
Now suppose that Joe wants his middle name initial used, and Jane
prefers her family name fully spelled out. A proper
would look like:
Jane Doe <jane@desktop.(none)> Joe R. Developer <email@example.com>
Note how there is no need for an entry for
<jane@laptop.(none)>, because the
real name of that author is already correct.
Example 2: Your repository contains commits from the following authors:
nick1 <firstname.lastname@example.org> nick2 <email@example.com> nick2 <firstname.lastname@example.org> santa <email@example.com> claus <firstname.lastname@example.org> CTO <email@example.com>
Then you might want a
.mailmap file that looks like:
<firstname.lastname@example.org> <email@example.com> Some Dude <firstname.lastname@example.org> nick1 <email@example.com> Other Author <firstname.lastname@example.org> nick2 <email@example.com> Other Author <firstname.lastname@example.org> <email@example.com> Santa Claus <firstname.lastname@example.org> <email@example.com>
Use hash # for comments that are either on their own line, or after the email address.
Part of the git suite