6 git-shortlog - Summarize 'git log' output
11 git log --pretty=short | 'git shortlog' [<options>]
12 'git shortlog' [<options>] [<revision range>] [[\--] <path>...]
16 Summarizes 'git log' output in a format suitable for inclusion
17 in release announcements. Each commit will be grouped by author and title.
19 Additionally, "[PATCH]" will be stripped from the commit description.
21 If no revisions are passed on the command line and either standard input
22 is not a terminal or there is no current branch, 'git shortlog' will
23 output a summary of the log read from standard input, without
24 reference to the current repository.
31 Sort output according to the number of commits per author instead
32 of author alphabetic order.
36 Suppress commit description and provide a commit count summary only.
40 Show the email address of each author.
43 Instead of the commit subject, use some other information to
44 describe each commit. '<format>' can be any string accepted
45 by the `--format` option of 'git log', such as '* [%h] %s'.
46 (See the "PRETTY FORMATS" section of linkgit:git-log[1].)
48 Each pretty-printed commit will be rewrapped before it is shown.
52 Collect and show committer identities instead of authors.
54 -w[<width>[,<indent1>[,<indent2>]]]::
55 Linewrap the output by wrapping each line at `width`. The first
56 line of each entry is indented by `indent1` spaces, and the second
57 and subsequent lines are indented by `indent2` spaces. `width`,
58 `indent1`, and `indent2` default to 76, 6 and 9 respectively.
60 If width is `0` (zero) then indent the lines of the output without wrapping
64 Show only commits in the specified revision range. When no
65 <revision range> is specified, it defaults to `HEAD` (i.e. the
66 whole history leading to the current commit). `origin..HEAD`
67 specifies all the commits reachable from the current commit
68 (i.e. `HEAD`), but not from `origin`. For a complete list of
69 ways to spell <revision range>, see the "Specifying Ranges"
70 section of linkgit:gitrevisions[7].
73 Consider only commits that are enough to explain how the files
74 that match the specified paths came to be.
76 Paths may need to be prefixed with "\-- " to separate them from
77 options or the revision range, when confusion arises.
82 The `.mailmap` feature is used to coalesce together commits by the same
83 person in the shortlog, where their name and/or email address was
86 include::mailmap.txt[]
90 Part of the linkgit:git[1] suite