]>
Commit | Line | Data |
---|---|---|
215a7ad1 JH |
1 | git-log(1) |
2 | ========== | |
3f971fc4 JH |
3 | |
4 | NAME | |
5 | ---- | |
215a7ad1 | 6 | git-log - Show commit logs |
3f971fc4 JH |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
7791a1d9 | 11 | [verse] |
933c758c | 12 | 'git log' [<options>] [<revision range>] [[--] <path>...] |
3f971fc4 JH |
13 | |
14 | DESCRIPTION | |
15 | ----------- | |
e51c3b50 JH |
16 | Shows the commit logs. |
17 | ||
bea86658 PB |
18 | :git-log: 1 |
19 | include::rev-list-description.txt[] | |
20 | ||
f8f28ed9 | 21 | The command takes options applicable to the linkgit:git-rev-list[1] |
e51c3b50 | 22 | command to control what is shown and how, and options applicable to |
f8f28ed9 | 23 | the linkgit:git-diff[1] command to control how the changes |
e51c3b50 JH |
24 | each commit introduces are shown. |
25 | ||
3f971fc4 JH |
26 | |
27 | OPTIONS | |
28 | ------- | |
5d1faf87 | 29 | |
4ded6916 EB |
30 | --follow:: |
31 | Continue listing the history of a file beyond renames | |
32 | (works only for a single file). | |
33 | ||
8a3d203b | 34 | --no-decorate:: |
462cbb41 | 35 | --decorate[=short|full|auto|no]:: |
33e7018c LH |
36 | Print out the ref names of any commits that are shown. If 'short' is |
37 | specified, the ref name prefixes 'refs/heads/', 'refs/tags/' and | |
38 | 'refs/remotes/' will not be printed. If 'full' is specified, the | |
462cbb41 RJ |
39 | full ref name (including prefix) will be printed. If 'auto' is |
40 | specified, then if the output is going to a terminal, the ref names | |
41 | are shown as if 'short' were given, otherwise no ref names are | |
42 | shown. The default option is 'short'. | |
56822cc9 | 43 | |
65516f58 RA |
44 | --decorate-refs=<pattern>:: |
45 | --decorate-refs-exclude=<pattern>:: | |
46 | If no `--decorate-refs` is given, pretend as if all refs were | |
47 | included. For each candidate, do not use it for decoration if it | |
48 | matches any patterns given to `--decorate-refs-exclude` or if it | |
a6be5e67 DS |
49 | doesn't match any of the patterns given to `--decorate-refs`. The |
50 | `log.excludeDecoration` config option allows excluding refs from | |
51 | the decorations, but an explicit `--decorate-refs` pattern will | |
52 | override a match in `log.excludeDecoration`. | |
65516f58 | 53 | |
30c4d7a7 NS |
54 | --source:: |
55 | Print out the ref name given on the command line by which each | |
56 | commit was reached. | |
57 | ||
88acccda | 58 | --[no-]mailmap:: |
2d9c5690 | 59 | --[no-]use-mailmap:: |
ea57bc0d | 60 | Use mailmap file to map author and committer names and email |
b20cc13e | 61 | addresses to canonical real names and email addresses. See |
ea57bc0d AP |
62 | linkgit:git-shortlog[1]. |
63 | ||
2e88c266 | 64 | --full-diff:: |
b20cc13e | 65 | Without this flag, `git log -p <path>...` shows commits that |
2e88c266 JN |
66 | touch the specified paths, and diffs about the same specified |
67 | paths. With this, the full diff is shown for commits that touch | |
f448e24e | 68 | the specified paths; this means that "<path>..." limits only |
2e88c266 | 69 | commits, and doesn't limit diff for those commits. |
b1c7946d MG |
70 | + |
71 | Note that this affects all diff-based output types, e.g. those | |
b20cc13e | 72 | produced by `--stat`, etc. |
2e88c266 | 73 | |
9fa3465d | 74 | --log-size:: |
c20e6fb1 JSJ |
75 | Include a line ``log size <number>'' in the output for each commit, |
76 | where <number> is the length of that commit's message in bytes. | |
77 | Intended to speed up tools that read log messages from `git log` | |
78 | output by allowing them to allocate space in advance. | |
9fa3465d | 79 | |
1e159833 | 80 | -L <start>,<end>:<file>:: |
d349e0ee | 81 | -L :<funcname>:<file>:: |
12da1d1f | 82 | Trace the evolution of the line range given by "<start>,<end>" |
d349e0ee | 83 | (or the function name regex <funcname>) within the <file>. You may |
13b8f68c TR |
84 | not give any pathspec limiters. This is currently limited to |
85 | a walk starting from a single revision, i.e., you may only | |
ace0f86c PB |
86 | give zero or one positive revision arguments, and |
87 | <start> and <end> (or <funcname>) must exist in the starting revision. | |
2be45868 PB |
88 | You can specify this option more than once. Implies `--patch`. |
89 | Patch output can be suppressed using `--no-patch`, but other diff formats | |
90 | (namely `--raw`, `--numstat`, `--shortstat`, `--dirstat`, `--summary`, | |
91 | `--name-only`, `--name-status`, `--check`) are not currently implemented. | |
0f483436 | 92 | + |
12da1d1f | 93 | include::line-range-format.txt[] |
12da1d1f | 94 | |
21a40b90 RR |
95 | <revision range>:: |
96 | Show only commits in the specified revision range. When no | |
97 | <revision range> is specified, it defaults to `HEAD` (i.e. the | |
98 | whole history leading to the current commit). `origin..HEAD` | |
99 | specifies all the commits reachable from the current commit | |
100 | (i.e. `HEAD`), but not from `origin`. For a complete list of | |
b20cc13e | 101 | ways to spell <revision range>, see the 'Specifying Ranges' |
21a40b90 | 102 | section of linkgit:gitrevisions[7]. |
a682187e | 103 | |
933c758c | 104 | [--] <path>...:: |
b15b5b10 | 105 | Show only commits that are enough to explain how the files |
b20cc13e JSJ |
106 | that match the specified paths came to be. See 'History |
107 | Simplification' below for details and other simplification | |
b15b5b10 TR |
108 | modes. |
109 | + | |
6955047f | 110 | Paths may need to be prefixed with `--` to separate them from |
00200e9e | 111 | options or the revision range, when confusion arises. |
e51c3b50 | 112 | |
f98fd436 MG |
113 | include::rev-list-options.txt[] |
114 | ||
115 | include::pretty-formats.txt[] | |
116 | ||
6f2e02ae JK |
117 | DIFF FORMATTING |
118 | --------------- | |
119 | ||
120 | By default, `git log` does not generate any diff output. The options | |
121 | below can be used to show the changes made by each commit. | |
122 | ||
5fbb4bc1 JK |
123 | Note that unless one of `-c`, `--cc`, or `-m` is given, merge commits |
124 | will never show a diff, even if a diff format like `--patch` is | |
125 | selected, nor will they match search options like `-S`. The exception is | |
126 | when `--first-parent` is in use, in which merges are treated like normal | |
127 | single-parent commits (this can be overridden by providing a | |
128 | combined-diff option or with `--no-diff-merges`). | |
129 | ||
6f2e02ae JK |
130 | -c:: |
131 | With this option, diff output for a merge commit | |
132 | shows the differences from each of the parents to the merge result | |
133 | simultaneously instead of showing pairwise diff between a parent | |
134 | and the result one at a time. Furthermore, it lists only files | |
135 | which were modified from all parents. | |
136 | ||
137 | --cc:: | |
138 | This flag implies the `-c` option and further compresses the | |
139 | patch output by omitting uninteresting hunks whose contents in | |
140 | the parents have only two variants and the merge result picks | |
141 | one of them without modification. | |
142 | ||
143 | --combined-all-paths:: | |
144 | This flag causes combined diffs (used for merge commits) to | |
145 | list the name of the file from all parents. It thus only has | |
146 | effect when -c or --cc are specified, and is likely only | |
147 | useful if filename changes are detected (i.e. when either | |
148 | rename or copy detection have been requested). | |
149 | ||
150 | -m:: | |
6f2e02ae JK |
151 | This flag makes the merge commits show the full diff like |
152 | regular commits; for each merge parent, a separate log entry | |
153 | and diff is generated. An exception is that only diff against | |
154 | the first parent is shown when `--first-parent` option is given; | |
155 | in that case, the output represents the changes the merge | |
156 | brought _into_ the then-current branch. | |
4ded6916 | 157 | |
405a2fdf SO |
158 | --diff-merges=off:: |
159 | --no-diff-merges:: | |
160 | Disable output of diffs for merge commits (default). Useful to | |
161 | override `-m`, `-c`, or `--cc`. | |
162 | ||
4ded6916 EB |
163 | :git-log: 1 |
164 | include::diff-options.txt[] | |
331b51d2 | 165 | |
272bd3cf | 166 | include::diff-generate-patch.txt[] |
331b51d2 | 167 | |
4ba258b7 | 168 | EXAMPLES |
bd663611 | 169 | -------- |
5d2fc913 | 170 | `git log --no-merges`:: |
bd663611 LT |
171 | |
172 | Show the whole commit history, but skip any merges | |
173 | ||
5d2fc913 | 174 | `git log v2.6.12.. include/scsi drivers/scsi`:: |
bd663611 LT |
175 | |
176 | Show all commits since version 'v2.6.12' that changed any file | |
b20cc13e | 177 | in the `include/scsi` or `drivers/scsi` subdirectories |
bd663611 | 178 | |
6cf378f0 | 179 | `git log --since="2 weeks ago" -- gitk`:: |
bd663611 LT |
180 | |
181 | Show the changes during the last two weeks to the file 'gitk'. | |
6955047f | 182 | The `--` is necessary to avoid confusion with the *branch* named |
bd663611 LT |
183 | 'gitk' |
184 | ||
5d2fc913 | 185 | `git log --name-status release..test`:: |
e51c3b50 JH |
186 | |
187 | Show the commits that are in the "test" branch but not yet | |
188 | in the "release" branch, along with the list of paths | |
189 | each commit modifies. | |
bd663611 | 190 | |
09b7e220 | 191 | `git log --follow builtin/rev-list.c`:: |
4f50f6a9 | 192 | |
b20cc13e | 193 | Shows the commits that changed `builtin/rev-list.c`, including |
4f50f6a9 SW |
194 | those commits that occurred before the file was given its |
195 | present name. | |
196 | ||
5d2fc913 | 197 | `git log --branches --not --remotes=origin`:: |
d08bae7e IL |
198 | |
199 | Shows all commits that are in any of local branches but not in | |
0e615b25 | 200 | any of remote-tracking branches for 'origin' (what you have that |
d08bae7e IL |
201 | origin doesn't). |
202 | ||
5d2fc913 | 203 | `git log master --not --remotes=*/master`:: |
d08bae7e IL |
204 | |
205 | Shows all commits that are in local master but not in any remote | |
206 | repository master branches. | |
207 | ||
5d2fc913 | 208 | `git log -p -m --first-parent`:: |
88d9d45d PB |
209 | |
210 | Shows the history including change diffs, but only from the | |
b20cc13e | 211 | ``main branch'' perspective, skipping commits that come from merged |
88d9d45d PB |
212 | branches, and showing full diffs of changes introduced by the merges. |
213 | This makes sense only when following a strict policy of merging all | |
214 | topic branches when staying on a single integration branch. | |
215 | ||
001b0976 | 216 | `git log -L '/int main/',/^}/:main.c`:: |
12da1d1f | 217 | |
b20cc13e | 218 | Shows how the function `main()` in the file `main.c` evolved |
12da1d1f TR |
219 | over time. |
220 | ||
70c2a258 | 221 | `git log -3`:: |
b20cc13e | 222 | |
70c2a258 | 223 | Limits the number of commits to show to 3. |
88d9d45d | 224 | |
4ba258b7 | 225 | DISCUSSION |
5dc7bcc2 JH |
226 | ---------- |
227 | ||
228 | include::i18n.txt[] | |
229 | ||
4ba258b7 | 230 | CONFIGURATION |
59893a88 JN |
231 | ------------- |
232 | ||
233 | See linkgit:git-config[1] for core variables and linkgit:git-diff[1] | |
234 | for settings related to diff generation. | |
235 | ||
236 | format.pretty:: | |
b20cc13e JSJ |
237 | Default for the `--format` option. (See 'Pretty Formats' above.) |
238 | Defaults to `medium`. | |
59893a88 JN |
239 | |
240 | i18n.logOutputEncoding:: | |
b20cc13e JSJ |
241 | Encoding to use when displaying logs. (See 'Discussion' above.) |
242 | Defaults to the value of `i18n.commitEncoding` if set, and UTF-8 | |
59893a88 JN |
243 | otherwise. |
244 | ||
245 | log.date:: | |
246 | Default format for human-readable dates. (Compare the | |
247 | `--date` option.) Defaults to "default", which means to write | |
248 | dates like `Sat May 8 19:35:34 2010 -0500`. | |
038a8788 SS |
249 | + |
250 | If the format is set to "auto:foo" and the pager is in use, format | |
251 | "foo" will be the used for the date format. Otherwise "default" will | |
252 | be used. | |
59893a88 | 253 | |
076c9837 | 254 | log.follow:: |
fd8d07ef EVW |
255 | If `true`, `git log` will act as if the `--follow` option was used when |
256 | a single <path> is given. This has the same limitations as `--follow`, | |
257 | i.e. it cannot be used to follow multiple files and does not work well | |
258 | on non-linear history. | |
076c9837 | 259 | |
da0005b8 | 260 | log.showRoot:: |
b20cc13e | 261 | If `false`, `git log` and related commands will not treat the |
59893a88 JN |
262 | initial commit as a big creation event. Any root commits in |
263 | `git log -p` output would be shown without a diff attached. | |
264 | The default is `true`. | |
265 | ||
fce04c3c MJ |
266 | log.showSignature:: |
267 | If `true`, `git log` and related commands will act as if the | |
268 | `--show-signature` option was passed to them. | |
269 | ||
d5422b0c | 270 | mailmap.*:: |
59893a88 JN |
271 | See linkgit:git-shortlog[1]. |
272 | ||
273 | notes.displayRef:: | |
274 | Which refs, in addition to the default set by `core.notesRef` | |
eee7f4a2 | 275 | or `GIT_NOTES_REF`, to read notes from when showing commit |
b20cc13e | 276 | messages with the `log` family of commands. See |
59893a88 JN |
277 | linkgit:git-notes[1]. |
278 | + | |
279 | May be an unabbreviated ref name or a glob and may be specified | |
280 | multiple times. A warning will be issued for refs that do not exist, | |
281 | but a glob that does not match any refs is silently ignored. | |
282 | + | |
ab18b2c0 | 283 | This setting can be disabled by the `--no-notes` option, |
eee7f4a2 | 284 | overridden by the `GIT_NOTES_DISPLAY_REF` environment variable, |
ab18b2c0 | 285 | and overridden by the `--notes=<ref>` option. |
5dc7bcc2 | 286 | |
3f971fc4 JH |
287 | GIT |
288 | --- | |
9e1f0a85 | 289 | Part of the linkgit:git[1] suite |