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