Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 184.108.40.206 → 2.1.0 no changes
- 220.127.116.11 01/13/14
- 18.104.22.168 → 22.214.171.124 no changes
- 1.8.3 05/24/13
- 126.96.36.199 → 188.8.131.52 no changes
- 184.108.40.206 04/07/13
- 220.127.116.11 → 18.104.22.168 no changes
- 22.214.171.124 01/14/13
- 1.8.1 no changes
- 126.96.36.199 12/27/12
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 09/30/12
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 05/25/12
- 188.8.131.52 → 184.108.40.206 no changes
- 1.7.5 04/24/11
git-shortlog - Summarize git log output
git log --pretty=short | 'git shortlog' [<options>] 'git shortlog' [<options>] [<revision range>] [[\--] <path>...]
Summarizes git log output in a format suitable for inclusion in release announcements. Each commit will be grouped by author and title.
Additionally, "[PATCH]" will be stripped from the commit description.
If no revisions are passed on the command line and either standard input is not a terminal or there is no current branch, git shortlog will output a summary of the log read from standard input, without reference to the current repository.
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.
Instead of the commit subject, use some other information to describe each commit. <format> can be any string accepted by the
--formatoption of git log, such as * [%h] %s. (See the "PRETTY FORMATS" section of git-log.)
Each pretty-printed commit will be rewrapped before it is shown.
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.
If width is
0(zero) then indent the lines of the output without wrapping them.
- <revision range>
Show only commits in the specified revision range. When no <revision range> is specified, it defaults to
HEAD(i.e. the whole history leading to the current commit).
origin..HEADspecifies all the commits reachable from the current commit (i.e.
HEAD), but not from
origin. For a complete list of ways to spell <revision range>, see the "Specifying Ranges" section of gitrevisions.
- [\--] <path>…
Consider only commits that are enough to explain how the files that match the specified paths came to be.
Paths may need to be prefixed with "-- " to separate them from options or the revision range, when confusion arises.
.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 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