6 git-log - Show commit logs
11 'git log' [<options>] [<since>..<until>] [[\--] <path>...]
15 Shows the commit logs.
17 The command takes options applicable to the 'git rev-list'
18 command to control what is shown and how, and options applicable to
19 the 'git diff-*' commands to control how the changes
20 each commit introduces are shown.
27 include::diff-options.txt[]
30 Limits the number of commits to show.
33 Show only commits between the named two commits. When
34 either <since> or <until> is omitted, it defaults to
35 `HEAD`, i.e. the tip of the current branch.
36 For a more complete list of ways to spell <since>
37 and <until>, see "SPECIFYING REVISIONS" section in
38 linkgit:git-rev-parse[1].
40 --decorate[=short|full]::
41 Print out the ref names of any commits that are shown. If 'short' is
42 specified, the ref name prefixes 'refs/heads/', 'refs/tags/' and
43 'refs/remotes/' will not be printed. If 'full' is specified, the
44 full ref name (including prefix) will be printed. The default option
48 Print out the ref name given on the command line by which each
52 Without this flag, "git log -p <path>..." shows commits that
53 touch the specified paths, and diffs about the same specified
54 paths. With this, the full diff is shown for commits that touch
55 the specified paths; this means that "<path>..." limits only
56 commits, and doesn't limit diff for those commits.
59 Continue listing the history of a file beyond renames.
62 Before the log message print out its size in bytes. Intended
63 mainly for porcelain tools consumption. If git is unable to
64 produce a valid value size is set to zero.
65 Note that only message is considered, if also a diff is shown
66 its size is not included.
69 Show only commits that affect any of the specified paths. To
70 prevent confusion with options and branch names, paths may need
71 to be prefixed with "\-- " to separate them from options or
75 include::rev-list-options.txt[]
77 include::pretty-formats.txt[]
79 include::diff-generate-patch.txt[]
85 Show the whole commit history, but skip any merges
87 git log v2.6.12.. include/scsi drivers/scsi::
89 Show all commits since version 'v2.6.12' that changed any file
90 in the include/scsi or drivers/scsi subdirectories
92 git log --since="2 weeks ago" \-- gitk::
94 Show the changes during the last two weeks to the file 'gitk'.
95 The "--" is necessary to avoid confusion with the *branch* named
98 git log --name-status release..test::
100 Show the commits that are in the "test" branch but not yet
101 in the "release" branch, along with the list of paths
102 each commit modifies.
104 git log --follow builtin-rev-list.c::
106 Shows the commits that changed builtin-rev-list.c, including
107 those commits that occurred before the file was given its
110 git log --branches --not --remotes=origin::
112 Shows all commits that are in any of local branches but not in
113 any of remote tracking branches for 'origin' (what you have that
116 git log master --not --remotes=*/master::
118 Shows all commits that are in local master but not in any remote
119 repository master branches.
121 git log -p -m --first-parent::
123 Shows the history including change diffs, but only from the
124 "main branch" perspective, skipping commits that come from merged
125 branches, and showing full diffs of changes introduced by the merges.
126 This makes sense only when following a strict policy of merging all
127 topic branches when staying on a single integration branch.
138 Written by Linus Torvalds <torvalds@osdl.org>
142 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
146 Part of the linkgit:git[1] suite