log -L: improve comments in process_all_files()
[git/git.git] / Documentation / git-log.txt
CommitLineData
215a7ad1
JH
1git-log(1)
2==========
3f971fc4
JH
3
4NAME
5----
215a7ad1 6git-log - Show commit logs
3f971fc4
JH
7
8
9SYNOPSIS
10--------
7791a1d9 11[verse]
b1524ee0 12'git log' [<options>] [<since>..<until>] [[\--] <path>...]
3f971fc4
JH
13
14DESCRIPTION
15-----------
e51c3b50
JH
16Shows the commit logs.
17
0b444cdb 18The command takes options applicable to the 'git rev-list'
e51c3b50 19command to control what is shown and how, and options applicable to
0b444cdb 20the 'git diff-*' commands to control how the changes
e51c3b50
JH
21each commit introduces are shown.
22
3f971fc4
JH
23
24OPTIONS
25-------
5d1faf87 26
3f971fc4 27<since>..<until>::
99e09cce
JH
28 Show only commits between the named two commits. When
29 either <since> or <until> is omitted, it defaults to
30 `HEAD`, i.e. the tip of the current branch.
41a5564e 31 For a more complete list of ways to spell <since>
9d83e382 32 and <until>, see linkgit:gitrevisions[7].
3f971fc4 33
4ded6916
EB
34--follow::
35 Continue listing the history of a file beyond renames
36 (works only for a single file).
37
8a3d203b
JH
38--no-decorate::
39--decorate[=short|full|no]::
33e7018c
LH
40 Print out the ref names of any commits that are shown. If 'short' is
41 specified, the ref name prefixes 'refs/heads/', 'refs/tags/' and
42 'refs/remotes/' will not be printed. If 'full' is specified, the
43 full ref name (including prefix) will be printed. The default option
44 is 'short'.
56822cc9 45
30c4d7a7
NS
46--source::
47 Print out the ref name given on the command line by which each
48 commit was reached.
49
ea57bc0d
AP
50--use-mailmap::
51 Use mailmap file to map author and committer names and email
52 to canonical real names and email addresses. See
53 linkgit:git-shortlog[1].
54
2e88c266 55--full-diff::
f448e24e 56 Without this flag, "git log -p <path>..." shows commits that
2e88c266
JN
57 touch the specified paths, and diffs about the same specified
58 paths. With this, the full diff is shown for commits that touch
f448e24e 59 the specified paths; this means that "<path>..." limits only
2e88c266 60 commits, and doesn't limit diff for those commits.
b1c7946d
MG
61+
62Note that this affects all diff-based output types, e.g. those
63produced by --stat etc.
2e88c266 64
9fa3465d
MC
65--log-size::
66 Before the log message print out its size in bytes. Intended
2de9b711 67 mainly for porcelain tools consumption. If Git is unable to
9fa3465d
MC
68 produce a valid value size is set to zero.
69 Note that only message is considered, if also a diff is shown
70 its size is not included.
71
13b8f68c
TR
72-L <start>,<end>:<file>, -L :<regex>:<file>::
73
12da1d1f 74 Trace the evolution of the line range given by "<start>,<end>"
13b8f68c
TR
75 (or the funcname regex <regex>) within the <file>. You may
76 not give any pathspec limiters. This is currently limited to
77 a walk starting from a single revision, i.e., you may only
78 give zero or one positive revision arguments.
12da1d1f
TR
79
80<start> and <end> can take one of these forms:
81
82include::line-range-format.txt[]
83You can specify this option more than once.
84
85
86--full-line-diff::
87 Always print the interesting range even if the current commit
88 does not change any line of the range.
89
b1524ee0 90[\--] <path>...::
b15b5b10
TR
91 Show only commits that are enough to explain how the files
92 that match the specified paths came to be. See "History
93 Simplification" below for details and other simplification
94 modes.
95+
96To prevent confusion with options and branch names, paths may need to
97be prefixed with "\-- " to separate them from options or refnames.
e51c3b50 98
f98fd436
MG
99include::rev-list-options.txt[]
100
101include::pretty-formats.txt[]
102
4ded6916 103Common diff options
f98fd436 104-------------------
4ded6916
EB
105
106:git-log: 1
107include::diff-options.txt[]
331b51d2 108
272bd3cf 109include::diff-generate-patch.txt[]
331b51d2 110
bd663611
LT
111Examples
112--------
5d2fc913 113`git log --no-merges`::
bd663611
LT
114
115 Show the whole commit history, but skip any merges
116
5d2fc913 117`git log v2.6.12.. include/scsi drivers/scsi`::
bd663611
LT
118
119 Show all commits since version 'v2.6.12' that changed any file
120 in the include/scsi or drivers/scsi subdirectories
121
6cf378f0 122`git log --since="2 weeks ago" -- gitk`::
bd663611
LT
123
124 Show the changes during the last two weeks to the file 'gitk'.
125 The "--" is necessary to avoid confusion with the *branch* named
126 'gitk'
127
5d2fc913 128`git log --name-status release..test`::
e51c3b50
JH
129
130 Show the commits that are in the "test" branch but not yet
131 in the "release" branch, along with the list of paths
132 each commit modifies.
bd663611 133
5d2fc913 134`git log --follow builtin-rev-list.c`::
4f50f6a9
SW
135
136 Shows the commits that changed builtin-rev-list.c, including
137 those commits that occurred before the file was given its
138 present name.
139
5d2fc913 140`git log --branches --not --remotes=origin`::
d08bae7e
IL
141
142 Shows all commits that are in any of local branches but not in
0e615b25 143 any of remote-tracking branches for 'origin' (what you have that
d08bae7e
IL
144 origin doesn't).
145
5d2fc913 146`git log master --not --remotes=*/master`::
d08bae7e
IL
147
148 Shows all commits that are in local master but not in any remote
149 repository master branches.
150
5d2fc913 151`git log -p -m --first-parent`::
88d9d45d
PB
152
153 Shows the history including change diffs, but only from the
154 "main branch" perspective, skipping commits that come from merged
155 branches, and showing full diffs of changes introduced by the merges.
156 This makes sense only when following a strict policy of merging all
157 topic branches when staying on a single integration branch.
158
12da1d1f
TR
159git log -L '/int main/',/^}/:main.c::
160
161 Shows how the function `main()` in the file 'main.c' evolved
162 over time.
163
70c2a258
NTND
164`git log -3`::
165 Limits the number of commits to show to 3.
88d9d45d 166
5dc7bcc2
JH
167Discussion
168----------
169
170include::i18n.txt[]
171
59893a88
JN
172Configuration
173-------------
174
175See linkgit:git-config[1] for core variables and linkgit:git-diff[1]
176for settings related to diff generation.
177
178format.pretty::
179 Default for the `--format` option. (See "PRETTY FORMATS" above.)
180 Defaults to "medium".
181
182i18n.logOutputEncoding::
183 Encoding to use when displaying logs. (See "Discussion", above.)
184 Defaults to the value of `i18n.commitEncoding` if set, UTF-8
185 otherwise.
186
187log.date::
188 Default format for human-readable dates. (Compare the
189 `--date` option.) Defaults to "default", which means to write
190 dates like `Sat May 8 19:35:34 2010 -0500`.
191
192log.showroot::
193 If `false`, 'git log' and related commands will not treat the
194 initial commit as a big creation event. Any root commits in
195 `git log -p` output would be shown without a diff attached.
196 The default is `true`.
197
d5422b0c 198mailmap.*::
59893a88
JN
199 See linkgit:git-shortlog[1].
200
201notes.displayRef::
202 Which refs, in addition to the default set by `core.notesRef`
203 or 'GIT_NOTES_REF', to read notes from when showing commit
204 messages with the 'log' family of commands. See
205 linkgit:git-notes[1].
206+
207May be an unabbreviated ref name or a glob and may be specified
208multiple times. A warning will be issued for refs that do not exist,
209but a glob that does not match any refs is silently ignored.
210+
ab18b2c0 211This setting can be disabled by the `--no-notes` option,
59893a88 212overridden by the 'GIT_NOTES_DISPLAY_REF' environment variable,
ab18b2c0 213and overridden by the `--notes=<ref>` option.
5dc7bcc2 214
3f971fc4
JH
215GIT
216---
9e1f0a85 217Part of the linkgit:git[1] suite