2 Show blank SHA-1 for boundary commits. This can also
3 be controlled via the `blame.blankboundary` config option.
6 Do not treat root commits as boundaries. This can also be
7 controlled via the `blame.showroot` config option.
10 Include additional statistics at the end of blame output.
13 Annotate only the given line range. <start> and <end> can take
16 include::line-range-format.txt[]
19 Show long rev (Default: off).
22 Show raw timestamp (Default: off).
25 Use revisions from revs-file instead of calling linkgit:git-rev-list[1].
28 Walk history forward instead of backward. Instead of showing
29 the revision in which a line appeared, this shows the last
30 revision in which a line has existed. This requires a range of
31 revision like START..END where the path to blame exists in
36 Show in a format designed for machine consumption.
39 Show the result incrementally in a format designed for
42 --encoding=<encoding>::
43 Specifies the encoding used to output author names
44 and commit summaries. Setting it to `none` makes blame
45 output unconverted data. For more information see the
46 discussion about encoding in the linkgit:git-log[1]
50 When <rev> is not specified, the command annotates the
51 changes starting backwards from the working tree copy.
52 This flag makes the command pretend as if the working
53 tree copy has the contents of the named file (specify
54 `-` to make the command read from the standard input).
57 The value is one of the following alternatives:
58 {relative,local,default,iso,rfc,short}. If --date is not
59 provided, the value of the blame.date config variable is
60 used. If the blame.date config variable is also not set, the
61 iso format is used. For more information, See the discussion
62 of the --date option at linkgit:git-log[1].
65 Detect moved or copied lines within a file. When a commit
66 moves or copies a block of lines (e.g. the original file
67 has A and then B, and the commit changes it to B and then
68 A), the traditional 'blame' algorithm notices only half of
69 the movement and typically blames the lines that were moved
70 up (i.e. B) to the parent and assigns blame to the lines that
71 were moved down (i.e. A) to the child commit. With this
72 option, both groups of lines are blamed on the parent by
73 running extra passes of inspection.
75 <num> is optional but it is the lower bound on the number of
76 alphanumeric characters that git must detect as moving/copying
77 within a file for it to associate those lines with the parent
78 commit. The default value is 20.
81 In addition to `-M`, detect lines moved or copied from other
82 files that were modified in the same commit. This is
83 useful when you reorganize your program and move code
84 around across files. When this option is given twice,
85 the command additionally looks for copies from other
86 files in the commit that creates the file. When this
87 option is given three times, the command additionally
88 looks for copies from other files in any commit.
90 <num> is optional but it is the lower bound on the number of
91 alphanumeric characters that git must detect as moving/copying
92 between files for it to associate those lines with the parent
93 commit. And the default value is 40. If there are more than one
94 `-C` options given, the <num> argument of the last `-C` will