Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.0.2 → 2.0.3 no changes
- 2.0.1 06/25/14
- 188.8.131.52 → 2.0.0 no changes
- 1.8.3 05/24/13
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 04/07/13
- 22.214.171.124 → 126.96.36.199 no changes
- 188.8.131.52 01/14/13
- 1.8.1 no changes
- 184.108.40.206 12/27/12
- 220.127.116.11 → 18.104.22.168 no changes
- 22.214.171.124 09/30/12
- 126.96.36.199 → 188.8.131.52 no changes
- 184.108.40.206 05/25/12
- 220.127.116.11 → 18.104.22.168 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 linkgit: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 linkgit: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
Part of the linkgit:git suite