Text of kernel.org › pub › software › scm › git › docs › git-shortlog.html as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

git-shortlog(1)

git-shortlog(1) Manual Page NAME git-shortlog - Summarize `git log` output SYNOPSIS git shortlog [ <options> ] [ <revision-range> ] [[ -- ] <path> …​] git log --pretty=short | git shortlog [ <options> ] DESCRIPTION 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. OPTIONS -n --numbered Sort output according to the number of commits per author instead of author alphabetic order. -s --summary Suppress commit description and provide a commit count summary only. -e --email Show the email address of each author. --format [ = <format> ] Instead of the commit subject, use some other information to describe each commit. <format> can be any string accepted by the --format option of git log , such as * [%h] %s . (See the PRETTY FORMATS section of git-log(1) .) Each pretty-printed commit will be rewrapped before it is shown. --date= <format> Show dates formatted according to the given date string. (See the --date option in the Commit Formatting section of git-log(1) ).

Useful with --group=format: <format> . --group= <type> Group commits based on <type> . If no --group option is specified, the default is author . <type> is one of: author , commits are grouped by author committer , commits are grouped by committer (the same as -c ) trailer: <field> , the <field> is interpreted as a case-insensitive commit message trailer (see git-interpret-trailers(1) ). For example, if your project uses Reviewed-by trailers, you might want to see who has been reviewing with git shortlog -ns --group=trailer:reviewed-by .

Note that commits that do not include the trailer will not be counted. Likewise, commits with multiple trailers (e.g., multiple signoffs) may be counted more than once (but only once per unique trailer value in that commit). Shortlog will attempt to parse each trailer value as a name <email> identity. If successful, the mailmap is applied and the email is omitted unless the --email option is specified. If the value cannot be parsed as an identity, it will be taken literally and completely. format: <format> , any string accepted by the --format option of git log . (See the PRETTY FORMATS section of git-log(1) .) If --group is specified multiple times, commits are counted under each value (but again, only once per unique value in that commit).

For example, git shortlog --group=author --group=trailer:co-authored-by counts both authors and co-authors. -c --committer This is an alias for --group=committer . -w [ <width> [ , <indent1> [ , <indent2> ]]] Linewrap the output by wrapping each line at width . The first line of each entry is indented by indent1 spaces, and the second and subsequent lines are indented by indent2 spaces. width , indent1 , and indent2 default 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 .. HEAD specifies 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(7) . [ -- ] <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. Commit Limiting Besides specifying a range of commits that should be listed using the special notations explained in the description, additional commit limiting may be applied. Using more options generally further limits the output (e.g. --since= <date1> limits to commits newer than <date1> , and using it with --grep= <pattern> further limits to commits whose log message has a line that matches <pattern> ), unless otherwise noted.

Note that these are applied before commit ordering and formatting options, such as --reverse . - <number> -n <number> --max-count= <number> Limit the output to the first <number> commits that would be shown. --max-count-oldest= <number> Limit the output to the last <number> commits that would be shown. --skip= <number> Skip <number> commits before starting to show the commit output. --since= <date> --after= <date> Show commits more recent than <date> .

As a special case, today means the last midnight. --since-as-filter= <date> Show all commits more recent than <date> . This visits all commits in the range, rather than stopping at the first commit which is older than <date> . --until= <date> --before= <date> Show commits older than <date> . --author= <pattern> --committer= <pattern> Limit the commits output to ones with author/committer header lines that match the <pattern> regular expression.

With more than one --author= <pattern> , commits whose author matches any of the <pattern> are chosen (similarly for multiple --committer= <pattern> ). --grep-reflog= <pattern> Limit the commits output to ones with reflog entries that match the <pattern> regular expression. With more than one --grep-reflog , commits whose reflog message matches any of the given patterns are chosen. It is an error to use this option unless --walk-reflogs is in use. --grep= <pattern> Limit the commits output to ones with a log message that matches the <pattern> regular expression.

With more than one --grep= <pattern> , commits whose message matches any of the <pattern> are chosen (but see --all-match ). When --notes is in effect, the message from the notes is matched as if it were part of the log message. --all-match Limit the commits output to ones that match all given --grep , instead of ones that match at least one. --invert-grep Limit the commits output to ones with a log message that do not match the <pattern> specified with --grep= <pattern> . -i --regexp-ignore-case Match the regular expression limiting patterns without regard to letter case. --basic-regexp Consider the limiting patterns to be basic regular expressions; this is the default. -E --extended-regexp Consider the limiting patterns to be extended regular expressions instead of the default basic regular expressions. -F --fixed-strings Consider the limiting patterns to be fixed strings (don’t interpret pattern as a regular expression). -P --perl-regexp Consider the limiting patterns to be Perl-compatible regular expressions.

Support for these types of regular expressions is an optional compile-time dependency. If Git wasn’t compiled with support for them providing this option will cause it to die. --remove-empty Stop when a given path disappears from the tree. --merges Print only merge commits. This is exactly the same as --min-parents=2 . --no-merges Do not print commits with more than one parent. This is exactly the same as --max-parents=1 . --min-parents= <number> --max-parents= <number> --no-min-parents --no-max-parents Show only commits which have at least (or at most) that many parent commits.

In particular, --max-parents=1 is the same as --no-merges , --min-parents=2 is the same as --merges . --max-parents=0 gives all root commits and --min-parents=3 all octopus merges. --no-min-parents and --no-max-parents reset these limits (to no limit) again. Equivalent forms are --min-parents=0 (any commit has 0 or more parents) and --max-parents=-1 (negative numbers denote no upper limit). --first-parent When finding commits to include, follow only the first parent commit upon seeing a merge commit.

This option can give a better overview when viewing the evolution of a particular topic branch, because merges into a

The rest of this page is on the live site.