| blob | 4d56373494a6e8a90a4aa0501b05fecd0f2c557f |
1 '\" t
2 .\" Title: git-blame
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
5 .\" Date: 2024-09-20
6 .\" Manual: Git Manual
7 .\" Source: Git 2.46.1.603.g94b60adee3
8 .\" Language: English
9 .\"
10 .TH "GIT\-BLAME" "1" "2024-09-20" "Git 2\&.46\&.1\&.603\&.g94b60a" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18 .ie \n(.g .ds Aq \(aq
19 .el .ds Aq '
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
24 .nh
25 .\" disable justification (adjust text to left margin only)
26 .ad l
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
30 .SH "NAME"
31 git-blame \- Show what revision and author last modified each line of a file
32 .SH "SYNOPSIS"
33 .sp
34 .nf
35 \fIgit blame\fR [\-c] [\-b] [\-l] [\-\-root] [\-t] [\-f] [\-n] [\-s] [\-e] [\-p] [\-w] [\-\-incremental]
36 [\-L <range>] [\-S <revs\-file>] [\-M] [\-C] [\-C] [\-C] [\-\-since=<date>]
37 [\-\-ignore\-rev <rev>] [\-\-ignore\-revs\-file <file>]
38 [\-\-color\-lines] [\-\-color\-by\-age] [\-\-progress] [\-\-abbrev=<n>]
39 [ \-\-contents <file> ] [<rev> | \-\-reverse <rev>\&.\&.<rev>] [\-\-] <file>
40 .fi
41 .SH "DESCRIPTION"
42 .sp
43 Annotates each line in the given file with information from the revision which last modified the line\&. Optionally, start annotating from the given revision\&.
44 .sp
45 When specified one or more times, \fB\-L\fR restricts annotation to the requested lines\&.
46 .sp
47 The origin of lines is automatically followed across whole\-file renames (currently there is no option to turn the rename\-following off)\&. To follow lines moved from one file to another, or to follow lines that were copied and pasted from another file, etc\&., see the \fB\-C\fR and \fB\-M\fR options\&.
48 .sp
49 The report does not tell you anything about lines which have been deleted or replaced; you need to use a tool such as \fIgit diff\fR or the "pickaxe" interface briefly mentioned in the following paragraph\&.
50 .sp
51 Apart from supporting file annotation, Git also supports searching the development history for when a code snippet occurred in a change\&. This makes it possible to track when a code snippet was added to a file, moved or copied between files, and eventually deleted or replaced\&. It works by searching for a text string in the diff\&. A small example of the pickaxe interface that searches for \fBblame_usage\fR:
52 .sp
53 .if n \{\
54 .RS 4
55 .\}
56 .nf
57 $ git log \-\-pretty=oneline \-S\*(Aqblame_usage\*(Aq
58 5040f17eba15504bad66b14a645bddd9b015ebb7 blame \-S <ancestry\-file>
59 ea4c7f9bf69e781dd0cd88d2bccb2bf5cc15c9a7 git\-blame: Make the output
60 .fi
61 .if n \{\
62 .RE
63 .\}
64 .SH "OPTIONS"
65 .PP
66 \-b
67 .RS 4
68 Show blank SHA\-1 for boundary commits\&. This can also be controlled via the
69 \fBblame\&.blankBoundary\fR
70 config option\&.
71 .RE
72 .PP
73 \-\-root
74 .RS 4
75 Do not treat root commits as boundaries\&. This can also be controlled via the
76 \fBblame\&.showRoot\fR
77 config option\&.
78 .RE
79 .PP
80 \-\-show\-stats
81 .RS 4
82 Include additional statistics at the end of blame output\&.
83 .RE
84 .PP
85 \-L <start>,<end>, \-L :<funcname>
86 .RS 4
87 Annotate only the line range given by
88 \fI<start>,<end>\fR, or by the function name regex
89 \fI<funcname>\fR\&. May be specified multiple times\&. Overlapping ranges are allowed\&.
90 .sp
91 \fI<start>\fR
92 and
93 \fI<end>\fR
94 are optional\&.
95 \fB\-L <start>\fR
96 or
97 \fB\-L <start>,\fR
98 spans from
99 \fI<start>\fR
100 to end of file\&.
101 \fB\-L ,<end>\fR
102 spans from start of file to
103 \fI<end>\fR\&.
104 .sp
105 \fI<start>\fR
106 and
107 \fI<end>\fR
108 can take one of these forms:
109 .sp
110 .RS 4
111 .ie n \{\
112 \h'-04'\(bu\h'+03'\c
113 .\}
114 .el \{\
115 .sp -1
116 .IP \(bu 2.3
117 .\}
118 number
119 .sp
120 If
121 \fI<start>\fR
122 or
123 \fI<end>\fR
124 is a number, it specifies an absolute line number (lines count from 1)\&.
125 .RE
126 .sp
127 .RS 4
128 .ie n \{\
129 \h'-04'\(bu\h'+03'\c
130 .\}
131 .el \{\
132 .sp -1
133 .IP \(bu 2.3
134 .\}
135 \fB/regex/\fR
136 .sp
137 This form will use the first line matching the given POSIX regex\&. If
138 \fI<start>\fR
139 is a regex, it will search from the end of the previous
140 \fB\-L\fR
141 range, if any, otherwise from the start of file\&. If
142 \fI<start>\fR
143 is
144 \fB^/regex/\fR, it will search from the start of file\&. If
145 \fI<end>\fR
146 is a regex, it will search starting at the line given by
147 \fI<start>\fR\&.
148 .RE
149 .sp
150 .RS 4
151 .ie n \{\
152 \h'-04'\(bu\h'+03'\c
153 .\}
154 .el \{\
155 .sp -1
156 .IP \(bu 2.3
157 .\}
158 +offset or \-offset
159 .sp
160 This is only valid for
161 \fI<end>\fR
162 and will specify a number of lines before or after the line given by
163 \fI<start>\fR\&.
164 .RE
165 .sp
166 If
167 \fB:<funcname>\fR
168 is given in place of
169 \fI<start>\fR
170 and
171 \fI<end>\fR, it is a regular expression that denotes the range from the first funcname line that matches
172 \fI<funcname>\fR, up to the next funcname line\&.
173 \fB:<funcname>\fR
174 searches from the end of the previous
175 \fB\-L\fR
176 range, if any, otherwise from the start of file\&.
177 \fB^:<funcname>\fR
178 searches from the start of file\&. The function names are determined in the same way as
179 \fBgit diff\fR
180 works out patch hunk headers (see
181 \fIDefining a custom hunk\-header\fR
182 in
183 \fBgitattributes\fR(5))\&.
184 .RE
185 .PP
186 \-l
187 .RS 4
188 Show long rev (Default: off)\&.
189 .RE
190 .PP
191 \-t
192 .RS 4
193 Show raw timestamp (Default: off)\&.
194 .RE
195 .PP
196 \-S <revs\-file>
197 .RS 4
198 Use revisions from revs\-file instead of calling
199 \fBgit-rev-list\fR(1)\&.
200 .RE
201 .PP
202 \-\-reverse <rev>\&.\&.<rev>
203 .RS 4
204 Walk history forward instead of backward\&. Instead of showing the revision in which a line appeared, this shows the last revision in which a line has existed\&. This requires a range of revision like START\&.\&.END where the path to blame exists in START\&.
205 \fBgit blame \-\-reverse START\fR
206 is taken as
207 \fBgit blame \-\-reverse START\&.\&.HEAD\fR
208 for convenience\&.
209 .RE
210 .PP
211 \-\-first\-parent
212 .RS 4
213 Follow only the first parent commit upon seeing a merge commit\&. This option can be used to determine when a line was introduced to a particular integration branch, rather than when it was introduced to the history overall\&.
214 .RE
215 .PP
216 \-p, \-\-porcelain
217 .RS 4
218 Show in a format designed for machine consumption\&.
219 .RE
220 .PP
221 \-\-line\-porcelain
222 .RS 4
223 Show the porcelain format, but output commit information for each line, not just the first time a commit is referenced\&. Implies \-\-porcelain\&.
224 .RE
225 .PP
226 \-\-incremental
227 .RS 4
228 Show the result incrementally in a format designed for machine consumption\&.
229 .RE
230 .PP
231 \-\-encoding=<encoding>
232 .RS 4
233 Specifies the encoding used to output author names and commit summaries\&. Setting it to
234 \fBnone\fR
235 makes blame output unconverted data\&. For more information see the discussion about encoding in the
236 \fBgit-log\fR(1)
237 manual page\&.
238 .RE
239 .PP
240 \-\-contents <file>
241 .RS 4
242 Annotate using the contents from the named file, starting from <rev> if it is specified, and HEAD otherwise\&. You may specify
243 \fI\-\fR
244 to make the command read from the standard input for the file contents\&.
245 .RE
246 .PP
247 \-\-date <format>
248 .RS 4
249 Specifies the format used to output dates\&. If \-\-date is not provided, the value of the blame\&.date config variable is used\&. If the blame\&.date config variable is also not set, the iso format is used\&. For supported values, see the discussion of the \-\-date option at
250 \fBgit-log\fR(1)\&.
251 .RE
252 .PP
253 \-\-[no\-]progress
254 .RS 4
255 Progress status is reported on the standard error stream by default when it is attached to a terminal\&. This flag enables progress reporting even if not attached to a terminal\&. Can\(cqt use
256 \fB\-\-progress\fR
257 together with
258 \fB\-\-porcelain\fR
259 or
260 \fB\-\-incremental\fR\&.
261 .RE
262 .PP
263 \-M[<num>]
264 .RS 4
265 Detect moved or copied lines within a file\&. When a commit moves or copies a block of lines (e\&.g\&. the original file has A and then B, and the commit changes it to B and then A), the traditional
266 \fIblame\fR
267 algorithm notices only half of the movement and typically blames the lines that were moved up (i\&.e\&. B) to the parent and assigns blame to the lines that were moved down (i\&.e\&. A) to the child commit\&. With this option, both groups of lines are blamed on the parent by running extra passes of inspection\&.
268 .sp
269 <num> is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as moving/copying within a file for it to associate those lines with the parent commit\&. The default value is 20\&.
270 .RE
271 .PP
272 \-C[<num>]
273 .RS 4
274 In addition to
275 \fB\-M\fR, detect lines moved or copied from other files that were modified in the same commit\&. This is useful when you reorganize your program and move code around across files\&. When this option is given twice, the command additionally looks for copies from other files in the commit that creates the file\&. When this option is given three times, the command additionally looks for copies from other files in any commit\&.
276 .sp
277 <num> is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as moving/copying between files for it to associate those lines with the parent commit\&. And the default value is 40\&. If there are more than one
278 \fB\-C\fR
279 options given, the <num> argument of the last
280 \fB\-C\fR
281 will take effect\&.
282 .RE
283 .PP
284 \-\-ignore\-rev <rev>
285 .RS 4
286 Ignore changes made by the revision when assigning blame, as if the change never happened\&. Lines that were changed or added by an ignored commit will be blamed on the previous commit that changed that line or nearby lines\&. This option may be specified multiple times to ignore more than one revision\&. If the
287 \fBblame\&.markIgnoredLines\fR
288 config option is set, then lines that were changed by an ignored commit and attributed to another commit will be marked with a
289 \fB?\fR
290 in the blame output\&. If the
291 \fBblame\&.markUnblamableLines\fR
292 config option is set, then those lines touched by an ignored commit that we could not attribute to another revision are marked with a
293 \fI*\fR\&.
294 .RE
295 .PP
296 \-\-ignore\-revs\-file <file>
297 .RS 4
298 Ignore revisions listed in
299 \fBfile\fR, which must be in the same format as an
300 \fBfsck\&.skipList\fR\&. This option may be repeated, and these files will be processed after any files specified with the
301 \fBblame\&.ignoreRevsFile\fR
302 config option\&. An empty file name,
303 \fB""\fR, will clear the list of revs from previously processed files\&.
304 .RE
305 .PP
306 \-\-color\-lines
307 .RS 4
308 Color line annotations in the default format differently if they come from the same commit as the preceding line\&. This makes it easier to distinguish code blocks introduced by different commits\&. The color defaults to cyan and can be adjusted using the
309 \fBcolor\&.blame\&.repeatedLines\fR
310 config option\&.
311 .RE
312 .PP
313 \-\-color\-by\-age
314 .RS 4
315 Color line annotations depending on the age of the line in the default format\&. The
316 \fBcolor\&.blame\&.highlightRecent\fR
317 config option controls what color is used for each range of age\&.
318 .RE
319 .PP
320 \-h
321 .RS 4
322 Show help message\&.
323 .RE
324 .PP
325 \-c
326 .RS 4
327 Use the same output mode as
328 \fBgit-annotate\fR(1)
329 (Default: off)\&.
330 .RE
331 .PP
332 \-\-score\-debug
333 .RS 4
334 Include debugging information related to the movement of lines between files (see
335 \fB\-C\fR) and lines moved within a file (see
336 \fB\-M\fR)\&. The first number listed is the score\&. This is the number of alphanumeric characters detected as having been moved between or within files\&. This must be above a certain threshold for
337 \fIgit blame\fR
338 to consider those lines of code to have been moved\&.
339 .RE
340 .PP
341 \-f, \-\-show\-name
342 .RS 4
343 Show the filename in the original commit\&. By default the filename is shown if there is any line that came from a file with a different name, due to rename detection\&.
344 .RE
345 .PP
346 \-n, \-\-show\-number
347 .RS 4
348 Show the line number in the original commit (Default: off)\&.
349 .RE
350 .PP
351 \-s
352 .RS 4
353 Suppress the author name and timestamp from the output\&.
354 .RE
355 .PP
356 \-e, \-\-show\-email
357 .RS 4
358 Show the author email instead of the author name (Default: off)\&. This can also be controlled via the
359 \fBblame\&.showEmail\fR
360 config option\&.
361 .RE
362 .PP
363 \-w
364 .RS 4
365 Ignore whitespace when comparing the parent\(cqs version and the child\(cqs to find where the lines came from\&.
366 .RE
367 .PP
368 \-\-abbrev=<n>
369 .RS 4
370 Instead of using the default 7+1 hexadecimal digits as the abbreviated object name, use <m>+1 digits, where <m> is at least <n> but ensures the commit object names are unique\&. Note that 1 column is used for a caret to mark the boundary commit\&.
371 .RE
372 .SH "THE DEFAULT FORMAT"
373 .sp
374 When neither \fB\-\-porcelain\fR nor \fB\-\-incremental\fR option is specified, \fBgit blame\fR will output annotation for each line with:
375 .sp
376 .RS 4
377 .ie n \{\
378 \h'-04'\(bu\h'+03'\c
379 .\}
380 .el \{\
381 .sp -1
382 .IP \(bu 2.3
383 .\}
384 abbreviated object name for the commit the line came from;
385 .RE
386 .sp
387 .RS 4
388 .ie n \{\
389 \h'-04'\(bu\h'+03'\c
390 .\}
391 .el \{\
392 .sp -1
393 .IP \(bu 2.3
394 .\}
395 author ident (by default the author name and date, unless
396 \fB\-s\fR
397 or
398 \fB\-e\fR
399 is specified); and
400 .RE
401 .sp
402 .RS 4
403 .ie n \{\
404 \h'-04'\(bu\h'+03'\c
405 .\}
406 .el \{\
407 .sp -1
408 .IP \(bu 2.3
409 .\}
410 line number
411 .RE
412 .sp
413 before the line contents\&.
414 .SH "THE PORCELAIN FORMAT"
415 .sp
416 In this format, each line is output after a header; the header at the minimum has the first line which has:
417 .sp
418 .RS 4
419 .ie n \{\
420 \h'-04'\(bu\h'+03'\c
421 .\}
422 .el \{\
423 .sp -1
424 .IP \(bu 2.3
425 .\}
426 40\-byte SHA\-1 of the commit the line is attributed to;
427 .RE
428 .sp
429 .RS 4
430 .ie n \{\
431 \h'-04'\(bu\h'+03'\c
432 .\}
433 .el \{\
434 .sp -1
435 .IP \(bu 2.3
436 .\}
437 the line number of the line in the original file;
438 .RE
439 .sp
440 .RS 4
441 .ie n \{\
442 \h'-04'\(bu\h'+03'\c
443 .\}
444 .el \{\
445 .sp -1
446 .IP \(bu 2.3
447 .\}
448 the line number of the line in the final file;
449 .RE
450 .sp
451 .RS 4
452 .ie n \{\
453 \h'-04'\(bu\h'+03'\c
454 .\}
455 .el \{\
456 .sp -1
457 .IP \(bu 2.3
458 .\}
459 on a line that starts a group of lines from a different commit than the previous one, the number of lines in this group\&. On subsequent lines this field is absent\&.
460 .RE
461 .sp
462 This header line is followed by the following information at least once for each commit:
463 .sp
464 .RS 4
465 .ie n \{\
466 \h'-04'\(bu\h'+03'\c
467 .\}
468 .el \{\
469 .sp -1
470 .IP \(bu 2.3
471 .\}
472 the author name ("author"), email ("author\-mail"), time ("author\-time"), and time zone ("author\-tz"); similarly for committer\&.
473 .RE
474 .sp
475 .RS 4
476 .ie n \{\
477 \h'-04'\(bu\h'+03'\c
478 .\}
479 .el \{\
480 .sp -1
481 .IP \(bu 2.3
482 .\}
483 the filename in the commit that the line is attributed to\&.
484 .RE
485 .sp
486 .RS 4
487 .ie n \{\
488 \h'-04'\(bu\h'+03'\c
489 .\}
490 .el \{\
491 .sp -1
492 .IP \(bu 2.3
493 .\}
494 the first line of the commit log message ("summary")\&.
495 .RE
496 .sp
497 The contents of the actual line are output after the above header, prefixed by a TAB\&. This is to allow adding more header elements later\&.
498 .sp
499 The porcelain format generally suppresses commit information that has already been seen\&. For example, two lines that are blamed to the same commit will both be shown, but the details for that commit will be shown only once\&. This is more efficient, but may require more state be kept by the reader\&. The \fB\-\-line\-porcelain\fR option can be used to output full commit information for each line, allowing simpler (but less efficient) usage like:
500 .sp
501 .if n \{\
502 .RS 4
503 .\}
504 .nf
505 # count the number of lines attributed to each author
506 git blame \-\-line\-porcelain file |
507 sed \-n \*(Aqs/^author //p\*(Aq |
508 sort | uniq \-c | sort \-rn
509 .fi
510 .if n \{\
511 .RE
512 .\}
513 .SH "SPECIFYING RANGES"
514 .sp
515 Unlike \fIgit blame\fR and \fIgit annotate\fR in older versions of git, the extent of the annotation can be limited to both line ranges and revision ranges\&. The \fB\-L\fR option, which limits annotation to a range of lines, may be specified multiple times\&.
516 .sp
517 When you are interested in finding the origin for lines 40\-60 for file \fBfoo\fR, you can use the \fB\-L\fR option like so (they mean the same thing \(em both ask for 21 lines starting at line 40):
518 .sp
519 .if n \{\
520 .RS 4
521 .\}
522 .nf
523 git blame \-L 40,60 foo
524 git blame \-L 40,+21 foo
525 .fi
526 .if n \{\
527 .RE
528 .\}
529 .sp
530 Also you can use a regular expression to specify the line range:
531 .sp
532 .if n \{\
533 .RS 4
534 .\}
535 .nf
536 git blame \-L \*(Aq/^sub hello {/,/^}$/\*(Aq foo
537 .fi
538 .if n \{\
539 .RE
540 .\}
541 .sp
542 which limits the annotation to the body of the \fBhello\fR subroutine\&.
543 .sp
544 When you are not interested in changes older than version v2\&.6\&.18, or changes older than 3 weeks, you can use revision range specifiers similar to \fIgit rev\-list\fR:
545 .sp
546 .if n \{\
547 .RS 4
548 .\}
549 .nf
550 git blame v2\&.6\&.18\&.\&. \-\- foo
551 git blame \-\-since=3\&.weeks \-\- foo
552 .fi
553 .if n \{\
554 .RE
555 .\}
556 .sp
557 When revision range specifiers are used to limit the annotation, lines that have not changed since the range boundary (either the commit v2\&.6\&.18 or the most recent commit that is more than 3 weeks old in the above example) are blamed for that range boundary commit\&.
558 .sp
559 A particularly useful way is to see if an added file has lines created by copy\-and\-paste from existing files\&. Sometimes this indicates that the developer was being sloppy and did not refactor the code properly\&. You can first find the commit that introduced the file with:
560 .sp
561 .if n \{\
562 .RS 4
563 .\}
564 .nf
565 git log \-\-diff\-filter=A \-\-pretty=short \-\- foo
566 .fi
567 .if n \{\
568 .RE
569 .\}
570 .sp
571 and then annotate the change between the commit and its parents, using \fBcommit^!\fR notation:
572 .sp
573 .if n \{\
574 .RS 4
575 .\}
576 .nf
577 git blame \-C \-C \-f $commit^! \-\- foo
578 .fi
579 .if n \{\
580 .RE
581 .\}
582 .SH "INCREMENTAL OUTPUT"
583 .sp
584 When called with \fB\-\-incremental\fR option, the command outputs the result as it is built\&. The output generally will talk about lines touched by more recent commits first (i\&.e\&. the lines will be annotated out of order) and is meant to be used by interactive viewers\&.
585 .sp
586 The output format is similar to the Porcelain format, but it does not contain the actual lines from the file that is being annotated\&.
587 .sp
588 .RS 4
589 .ie n \{\
590 \h'-04' 1.\h'+01'\c
591 .\}
592 .el \{\
593 .sp -1
594 .IP " 1." 4.2
595 .\}
596 Each blame entry always starts with a line of:
597 .sp
598 .if n \{\
599 .RS 4
600 .\}
601 .nf
602 <40\-byte\-hex\-sha1> <sourceline> <resultline> <num\-lines>
603 .fi
604 .if n \{\
605 .RE
606 .\}
607 .sp
608 Line numbers count from 1\&.
609 .RE
610 .sp
611 .RS 4
612 .ie n \{\
613 \h'-04' 2.\h'+01'\c
614 .\}
615 .el \{\
616 .sp -1
617 .IP " 2." 4.2
618 .\}
619 The first time that a commit shows up in the stream, it has various other information about it printed out with a one\-word tag at the beginning of each line describing the extra commit information (author, email, committer, dates, summary, etc\&.)\&.
620 .RE
621 .sp
622 .RS 4
623 .ie n \{\
624 \h'-04' 3.\h'+01'\c
625 .\}
626 .el \{\
627 .sp -1
628 .IP " 3." 4.2
629 .\}
630 Unlike the Porcelain format, the filename information is always given and terminates the entry:
631 .sp
632 .if n \{\
633 .RS 4
634 .\}
635 .nf
636 "filename" <whitespace\-quoted\-filename\-goes\-here>
637 .fi
638 .if n \{\
639 .RE
640 .\}
641 .sp
642 and thus it is really quite easy to parse for some line\- and word\-oriented parser (which should be quite natural for most scripting languages)\&.
643 .if n \{\
644 .sp
645 .\}
646 .RS 4
647 .it 1 an-trap
648 .nr an-no-space-flag 1
649 .nr an-break-flag 1
650 .br
651 .ps +1
652 \fBNote\fR
653 .ps -1
654 .br
655 For people who do parsing: to make it more robust, just ignore any lines between the first and last one ("<sha1>" and "filename" lines) where you do not recognize the tag words (or care about that particular one) at the beginning of the "extended information" lines\&. That way, if there is ever added information (like the commit encoding or extended commit commentary), a blame viewer will not care\&.
656 .sp .5v
657 .RE
658 .RE
659 .SH "MAPPING AUTHORS"
660 .sp
661 See \fBgitmailmap\fR(5)\&.
662 .SH "CONFIGURATION"
663 .sp
664 Everything below this line in this section is selectively included from the \fBgit-config\fR(1) documentation\&. The content is the same as what\(cqs found there:
665 .PP
666 blame\&.blankBoundary
667 .RS 4
668 Show blank commit object name for boundary commits in
669 \fBgit-blame\fR(1)\&. This option defaults to false\&.
670 .RE
671 .PP
672 blame\&.coloring
673 .RS 4
674 This determines the coloring scheme to be applied to blame output\&. It can be
675 \fIrepeatedLines\fR,
676 \fIhighlightRecent\fR, or
677 \fInone\fR
678 which is the default\&.
679 .RE
680 .PP
681 blame\&.date
682 .RS 4
683 Specifies the format used to output dates in
684 \fBgit-blame\fR(1)\&. If unset the iso format is used\&. For supported values, see the discussion of the
685 \fB\-\-date\fR
686 option at
687 \fBgit-log\fR(1)\&.
688 .RE
689 .PP
690 blame\&.showEmail
691 .RS 4
692 Show the author email instead of author name in
693 \fBgit-blame\fR(1)\&. This option defaults to false\&.
694 .RE
695 .PP
696 blame\&.showRoot
697 .RS 4
698 Do not treat root commits as boundaries in
699 \fBgit-blame\fR(1)\&. This option defaults to false\&.
700 .RE
701 .PP
702 blame\&.ignoreRevsFile
703 .RS 4
704 Ignore revisions listed in the file, one unabbreviated object name per line, in
705 \fBgit-blame\fR(1)\&. Whitespace and comments beginning with
706 \fB#\fR
707 are ignored\&. This option may be repeated multiple times\&. Empty file names will reset the list of ignored revisions\&. This option will be handled before the command line option
708 \fB\-\-ignore\-revs\-file\fR\&.
709 .RE
710 .PP
711 blame\&.markUnblamableLines
712 .RS 4
713 Mark lines that were changed by an ignored revision that we could not attribute to another commit with a
714 \fI*\fR
715 in the output of
716 \fBgit-blame\fR(1)\&.
717 .RE
718 .PP
719 blame\&.markIgnoredLines
720 .RS 4
721 Mark lines that were changed by an ignored revision that we attributed to another commit with a
722 \fI?\fR
723 in the output of
724 \fBgit-blame\fR(1)\&.
725 .RE
726 .SH "SEE ALSO"
727 .sp
728 \fBgit-annotate\fR(1)
729 .SH "GIT"
730 .sp
731 Part of the \fBgit\fR(1) suite