Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.12.1 → 2.13.3 no changes
- 2.12.0 02/24/17
git log --pretty=short | git shortlog [-h] [-n] [-s] [-e] [-w] git shortlog [-n|--numbered] [-s|--summary] [-e|--email] [-w[<width>[,<indent1>[,<indent2>]]]] [<committish>…]
Summarizes git-log output in a format suitable for inclusion in release announcements. Each commit will be grouped by author and the first line of the commit message will be shown.
Additionally, "[PATCH]" will be stripped from the commit description.
Print a short usage message and exit.
Sort output according to the number of commits per author instead of author alphabetic order.
Suppress commit description and provide a commit count summary only.
Show the email address of each author.
Linewrap the output by wrapping each line at
width. The first line of each entry is indented by
indent1spaces, and the second and subsequent lines are indented by
indent2default to 76, 6 and 9 respectively.
.mailmap feature is used to coalesce together commits by the same
person in the shortlog, where their name and/or email address was
If the file
.mailmap exists at the toplevel of the repository, or at
the location pointed to by the mailmap.file configuration option, 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. Thus, looks like this
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 we don’t need an entry for <jane@laptop.(none)>, because the real name of that author is correct already.
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 looking 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.
Written by Jeff Garzik <firstname.lastname@example.org>
Part of the git suite