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 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 option in the "Commit Formatting" section of git-log(1)). Useful with .

--group=<type>

Group commits based on . If no option is specified, the default is . is one of:

  • , commits are grouped by author

  • , commits are grouped by committer (the same as )

  • , the is interpreted as a case-insensitive commit message trailer (see git-interpret-trailers(1)). For example, if your project uses trailers, you might want to see who has been reviewing with .

  • , any string accepted by the option of git log. (See the "PRETTY FORMATS" section of git-log(1).)

    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 identity. If successful, the mailmap is applied and the email is omitted unless the option is specified. If the value cannot be parsed as an identity, it will be taken literally and completely.

If is specified multiple times, commits are counted under each value (but again, only once per unique value in that commit). For example, counts both authors and co-authors.

-c
--committer

This is an alias for .

-w[<width>[,<indent1>[,<indent2>]]]

Linewrap the output by wrapping each line at . The first line of each entry is indented by spaces, and the second and subsequent lines are indented by spaces. , , and default to 76, 6 and 9 respectively.

If width is (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 (i.e. the whole history leading to the current commit). specifies all the commits reachable from the current commit (i.e. ), but not from . 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. limits to commits newer than , and using it with further limits to commits whose log message has a line that matches ), unless otherwise noted.

Note that these are applied before commit ordering and formatting options, such as .

-<number>
-n <number>
--max-count=<number>

Limit the number of commits to output.

--skip=<number>

Skip number commits before starting to show the commit output.

--since=<date>
--after=<date>

Show commits more recent than a specific date.

--since-as-filter=<date>

Show all commits more recent than a specific date. This visits all commits in the range, rather than stopping at the first commit which is older than a specific date.

--until=<date>
--before=<date>

Show commits older than a specific date.

--author=<pattern>
--committer=<pattern>

Limit the commits output to ones with author/committer header lines that match the specified pattern (regular expression). With more than one , commits whose author matches any of the given patterns are chosen (similarly for multiple ).

--grep-reflog=<pattern>

Limit the commits output to ones with reflog entries that match the specified pattern (regular expression). With more than one , commits whose reflog message matches any of the given patterns are chosen. It is an error to use this option unless is in use.

--grep=<pattern>

Limit the commits output to ones with a log message that matches the specified pattern (regular expression). With more than one , commits whose message matches any of the given patterns are chosen (but see ).

When 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 , 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 .

-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 .

--no-merges

Do not print commits with more than one parent. This is exactly the same as .

--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, is the same as , is the same as . gives all root commits and all octopus merges.

and reset these limits (to no limit) again. Equivalent forms are (any commit has 0 or more parents) and (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 topic branch tend to be only about adjusting to updated upstream from time to time, and this option allows you to ignore the individual commits brought in to your history by such a merge.

--exclude-first-parent-only

When finding commits to exclude (with a ^), follow only the first parent commit upon seeing a merge commit. This can be used to find the set of changes in a topic branch from the point where it diverged from the remote branch, given that arbitrary merges can be valid topic branch changes.

--not

Reverses the meaning of the ^ prefix (or lack thereof) for all following revision specifiers, up to the next . When used on the command line before --stdin, the revisions passed through stdin will not be affected by it. Conversely, when passed via standard input, the revisions passed on the command line will not be affected by it.

--all

Pretend as if all the refs in , along with , are listed on the command line as <commit>.

--branches[=<pattern>]

Pretend as if all the refs in are listed on the command line as <commit>. If <pattern> is given, limit branches to ones matching given shell glob. If pattern lacks ?, *, or [, /* at the end is implied.

--tags[=<pattern>]

Pretend as if all the refs in are listed on the command line as <commit>. If <pattern> is given, limit tags to ones matching given shell glob. If pattern lacks ?, *, or [, /* at the end is implied.

--remotes[=<pattern>]

Pretend as if all the refs in are listed on the command line as <commit>. If <pattern> is given, limit remote-tracking branches to ones matching given shell glob. If pattern lacks ?, *, or [, /* at the end is implied.

--glob=<glob-pattern>

Pretend as if all the refs matching shell glob <glob-pattern> are listed on the command line as <commit>. Leading refs/, is automatically prepended if missing. If pattern lacks ?, *, or [, /* at the end is implied.

--exclude=<glob-pattern>

Do not include refs matching <glob-pattern> that the next , , , , or would otherwise consider. Repetitions of this option accumulate exclusion patterns up to the next , , , , or option (other options or arguments do not clear accumulated patterns).

The patterns given should not begin with , , or when applied to , , or , respectively, and they must begin with when applied to or . If a trailing /* is intended, it must be given explicitly.

--exclude-hidden=[fetch|receive|uploadpack]

Do not include refs that would be hidden by , or by consulting the appropriate , or configuration along with (see git-config(1)). This option affects the next pseudo-ref option or and is cleared after processing them.

--reflog

Pretend as if all objects mentioned by reflogs are listed on the command line as .

--alternate-refs

Pretend as if all objects mentioned as ref tips of alternate repositories were listed on the command line. An alternate repository is any repository whose object directory is specified in . The set of included objects may be modified by , etc. See git-config(1).

--single-worktree

By default, all working trees will be examined by the following options when there are more than one (see git-worktree(1)): , and . This option forces them to examine the current working tree only.

--ignore-missing

Upon seeing an invalid object name in the input, pretend as if the bad input was not given.

--bisect

Pretend as if the bad bisection ref was listed and as if it was followed by and the good bisection refs on the command line.

--stdin

In addition to getting arguments from the command line, read them from standard input as well. This accepts commits and pseudo-options like and . When a separator is seen, the following input is treated as paths and used to limit the result. Flags like which are read via standard input are only respected for arguments passed in the same way and will not influence any subsequent command line arguments.

--cherry-mark

Like (see below) but mark equivalent commits with rather than omitting them, and inequivalent ones with .

--cherry-pick

Omit any commit that introduces the same change as another commit on the “other side” when the set of commits are limited with symmetric difference.

For example, if you have two branches, and , a usual way to list all commits on only one side of them is with (see the example below in the description of the option). However, it shows the commits that were cherry-picked from the other branch (for example, “3rd on b” may be cherry-picked from branch A). With this option, such pairs of commits are excluded from the output.

--left-only
--right-only

List only commits on the respective side of a symmetric difference, i.e. only those which would be marked resp. by .

For example, omits those commits from which are in or are patch-equivalent to a commit in . In other words, this lists the commits from . More precisely, gives the exact list.

--cherry

A synonym for ; useful to limit the output to the commits on our side and mark those that have been applied to the other side of a forked history with , similar to .

-g
--walk-reflogs

Instead of walking the commit ancestry chain, walk reflog entries from the most recent one to older ones. When this option is used you cannot specify commits to exclude (that is, ^commit, commit1..commit2, and commit1...commit2 notations cannot be used).

With format other than and (for obvious reasons), this causes the output to have two extra lines of information taken from the reflog. The reflog designator in the output may be shown as (where <Nth> is the reverse-chronological index in the reflog) or as (with the <timestamp> for that entry), depending on a few rules:

  1. If the starting point is specified as , show the index format.

  2. If the starting point was specified as , show the timestamp format.

  3. If neither was used, but was given on the command line, show the timestamp in the format requested by .

  4. Otherwise, show the index format.

Under , the commit message is prefixed with this information on the same line. This option cannot be combined with . See also git-reflog(1).

Under , this information will not be shown at all.

--merge

Show commits touching conflicted paths in the range , where is the first existing pseudoref in , , or . Only works when the index has unmerged entries. This option can be used to show relevant commits when resolving conflicts from a 3-way merge.

--boundary

Output excluded boundary commits. Boundary commits are prefixed with .

History Simplification

Sometimes you are only interested in parts of the history, for example the commits modifying a particular <path>. But there are two parts of History Simplification, one part is selecting the commits and the other is how to do it, as there are various strategies to simplify the history.

The following options select the commits to be shown:

<paths>

Commits modifying the given <paths> are selected.

--simplify-by-decoration

Commits that are referred by some branch or tag are selected.

Note that extra commits can be shown to give a meaningful history.

The following options affect the way the simplification is performed:

Default mode

Simplifies the history to the simplest history explaining the final state of the tree. Simplest because it prunes some side branches if the end result is the same (i.e. merging branches with the same content)

--show-pulls

Include all commits from the default mode, but also any merge commits that are not TREESAME to the first parent but are TREESAME to a later parent. This mode is helpful for showing the merge commits that "first introduced" a change to a branch.

--full-history

Same as the default mode, but does not prune some history.

--dense

Only the selected commits are shown, plus some to have a meaningful history.

--sparse

All commits in the simplified history are shown.

--simplify-merges

Additional option to to remove some needless merges from the resulting history, as there are no selected commits contributing to this merge.

--ancestry-path[=<commit>]

When given a range of commits to display (e.g. commit1..commit2 or commit2 ^commit1), and a commit <commit> in that range, only display commits in that range that are ancestors of <commit>, descendants of <commit>, or <commit> itself. If no commit is specified, use commit1 (the excluded part of the range) as <commit>. Can be passed multiple times; if so, a commit is included if it is any of the commits given or if it is an ancestor or descendant of one of them.

A more detailed explanation follows.

Suppose you specified as the <paths>. We shall call commits that modify !TREESAME, and the rest TREESAME. (In a diff filtered for , they look different and equal, respectively.)

In the following, we will always refer to the same example history to illustrate the differences between simplification settings. We assume that you are filtering for a file in this commit graph:

          .-A---M---N---O---P---Q
         /     /   /   /   /   /
        I     B   C   D   E   Y
         \   /   /   /   /   /
          `-------------'   X

The horizontal line of history A---Q is taken to be the first parent of each merge. The commits are:

  • is the initial commit, in which exists with contents “asdf”, and a file exists with contents “quux”. Initial commits are compared to an empty tree, so is !TREESAME.

  • In , contains just “foo”.

  • contains the same change as . Its merge is trivial and hence TREESAME to all parents.

  • does not change , but its merge changes it to “foobar”, so it is not TREESAME to any parent.

  • sets to “baz”. Its merge combines the strings from and to “foobarbaz”; i.e., it is not TREESAME to any parent.

  • changes to “xyzzy”, and its merge combines the strings to “quux xyzzy”. is TREESAME to , but not to .

  • is an independent root commit that added a new file , and modified it. is TREESAME to . Its merge added to , and is TREESAME to , but not to .

walks backwards through history, including or excluding commits based on whether and/or parent rewriting (via or ) are used. The following settings are available.

Default mode

Commits are included if they are not TREESAME to any parent (though this can be changed, see below). If the commit was a merge, and it was TREESAME to one parent, follow only that parent. (Even if there are several TREESAME parents, follow only one of them.) Otherwise, follow all parents.

This results in:

          .-A---N---O
         /     /   /
        I---------D

Note how the rule to only follow the TREESAME parent, if one is available, removed from consideration entirely. was considered via , but is TREESAME. Root commits are compared to an empty tree, so is !TREESAME.

Parent/child relations are only visible with , but that does not affect the commits selected in default mode, so we have shown the parent lines.

--full-history without parent rewriting

This mode differs from the default in one point: always follow all parents of a merge, even if it is TREESAME to one of them. Even if more than one side of the merge has commits that are included, this does not imply that the merge itself is! In the example, we get

        I  A  B  N  D  O  P  Q

was excluded because it is TREESAME to both parents. , and were all walked, but only was !TREESAME, so the others do not appear.

Note that without parent rewriting, it is not really possible to talk about the parent/child relationships between the commits, so we show them disconnected.

--full-history with parent rewriting

Ordinary commits are only included if they are !TREESAME (though this can be changed, see below).

Merges are always included. However, their parent list is rewritten: Along each parent, prune away commits that are not included themselves. This results in

          .-A---M---N---O---P---Q
         /     /   /   /   /
        I     B   /   D   /
         \   /   /   /   /
          `-------------'

Compare to without rewriting above. Note that was pruned away because it is TREESAME, but the parent list of P was rewritten to contain 's parent . The same happened for and , and , and .

In addition to the above settings, you can change whether TREESAME affects inclusion:

--dense

Commits that are walked are included if they are not TREESAME to any parent.

--sparse

All commits that are walked are included.

Note that without , this still simplifies merges: if one of the parents is TREESAME, we follow only that one, so the other sides of the merge are never walked.

--simplify-merges

First, build a history graph in the same way that with parent rewriting does (see above).

Then simplify each commit to its replacement in the final history according to the following rules:

  • Set to .

  • Replace each parent of with its simplification . In the process, drop parents that are ancestors of other parents or that are root commits TREESAME to an empty tree, and remove duplicates, but take care to never drop all parents that we are TREESAME to.

  • If after this parent rewriting, is a root or merge commit (has zero or >1 parents), a boundary commit, or !TREESAME, it remains. Otherwise, it is replaced with its only parent.

The effect of this is best shown by way of comparing to with parent rewriting. The example turns into:

          .-A---M---N---O
         /     /       /
        I     B       D
         \   /       /
          `---------'

Note the major differences in , , and over :

  • 's parent list had removed, because it is an ancestor of the other parent . Still, remained because it is !TREESAME.

  • 's parent list similarly had removed. was then removed completely, because it had one parent and is TREESAME.

  • 's parent list had simplified to . was then removed, because it was a TREESAME root. was then removed completely, because it had one parent and is TREESAME.

There is another simplification mode available:

--ancestry-path[=<commit>]

Limit the displayed commits to those which are an ancestor of <commit>, or which are a descendant of <commit>, or are <commit> itself.

As an example use case, consider the following commit history:

            D---E-------F
           /     \       \
          B---C---G---H---I---J
         /                     \
        A-------K---------------L--M

A regular D..M computes the set of commits that are ancestors of , but excludes the ones that are ancestors of . This is useful to see what happened to the history leading to since , in the sense that “what does have that did not exist in ”. The result in this example would be all the commits, except and (and itself, of course).

When we want to find out what commits in are contaminated with the bug introduced by and need fixing, however, we might want to view only the subset of D..M that are actually descendants of , i.e. excluding and . This is exactly what the option does. Applied to the D..M range, it results in:

                E-------F
                 \       \
                  G---H---I---J
                               \
                                L--M

We can also use instead of which means the same thing when applied to the D..M range but is just more explicit.

If we instead are interested in a given topic within this range, and all commits affected by that topic, we may only want to view the subset of which contain that topic in their ancestry path. So, using for example would result in:

                E
                 \
                  G---H---I---J
                               \
                                L--M

Whereas would result in

                K---------------L--M

Before discussing another option, , we need to create a new example history.

A common problem users face when looking at simplified history is that a commit they know changed a file somehow does not appear in the file’s simplified history. Let’s demonstrate a new example and show how options such as and works in that case:

          .-A---M-----C--N---O---P
         /     / \  \  \/   /   /
        I     B   \  R-'`-Z'   /
         \   /     \/         /
          \ /      /\        /
           `---X--'  `---Y--'

For this example, suppose created which was modified by , , and in different ways. The single-parent commits , , and do not change . The merge commit was created by resolving the merge conflict to include both changes from and and hence is not TREESAME to either. The merge commit , however, was created by ignoring the contents of at and taking only the contents of at . Hence, is TREESAME to but not . Finally, the natural merge resolution to create is to take the contents of at , so is TREESAME to but not . The merge commits and are TREESAME to their first parents, but not to their second parents, and respectively.

When using the default mode, and both have a TREESAME parent, so those edges are walked and the others are ignored. The resulting history graph is:

        I---X

When using , Git walks every edge. This will discover the commits and and the merge , but also will reveal the merge commits and . With parent rewriting, the resulting graph is:

          .-A---M--------N---O---P
         /     / \  \  \/   /   /
        I     B   \  R-'`--'   /
         \   /     \/         /
          \ /      /\        /
           `---X--'  `------'

Here, the merge commits and contribute extra noise, as they did not actually contribute a change to . They only merged a topic that was based on an older version of . This is a common issue in repositories using a workflow where many contributors work in parallel and merge their topic branches along a single trunk: many unrelated merges appear in the results.

When using the option, the commits and disappear from the results. This is because the rewritten second parents of and are reachable from their first parents. Those edges are removed and then the commits look like single-parent commits that are TREESAME to their parent. This also happens to the commit , resulting in a history view as follows:

          .-A---M--.
         /     /    \
        I     B      R
         \   /      /
          \ /      /
           `---X--'

In this view, we see all of the important single-parent changes from , , and . We also see the carefully-resolved merge and the not-so-carefully-resolved merge . This is usually enough information to determine why the commits and "disappeared" from history in the default view. However, there are a few issues with this approach.

The first issue is performance. Unlike any previous option, the option requires walking the entire commit history before returning a single result. This can make the option difficult to use for very large repositories.

The second issue is one of auditing. When many contributors are working on the same repository, it is important which merge commits introduced a change into an important branch. The problematic merge above is not likely to be the merge commit that was used to merge into an important branch. Instead, the merge was used to merge and into the important branch. This commit may have information about why the change came to override the changes from and in its commit message.

--show-pulls

In addition to the commits shown in the default history, show each merge commit that is not TREESAME to its first parent but is TREESAME to a later parent.

When a merge commit is included by , the merge is treated as if it "pulled" the change from another branch. When using on this example (and no other options) the resulting graph is:

        I---X---R---N

Here, the merge commits and are included because they pulled the commits and into the base branch, respectively. These merges are the reason the commits and do not appear in the default history.

When is paired with , the graph includes all of the necessary information:

          .-A---M--.   N
         /     /    \ /
        I     B      R
         \   /      /
          \ /      /
           `---X--'

Notice that since is reachable from , the edge from to was simplified away. However, still appears in the history as an important commit because it "pulled" the change into the main branch.

The option allows you to view only the big picture of the topology of the history, by omitting commits that are not referenced by tags. Commits are marked as !TREESAME (in other words, kept after history simplification rules described above) if (1) they are referenced by tags, or (2) they change the contents of the paths given on the command line. All other commits are marked as TREESAME (subject to be simplified away).

MAPPING AUTHORS

Note that if is run outside of a repository (to process log contents on standard input), it will look for a file in the current directory.

GIT

Part of the git(1) suite