]>
Commit | Line | Data |
---|---|---|
635f4a30 AR |
1 | -b:: |
2 | Show blank SHA-1 for boundary commits. This can also | |
edaf10dd | 3 | be controlled via the `blame.blankBoundary` config option. |
635f4a30 AR |
4 | |
5 | --root:: | |
6 | Do not treat root commits as boundaries. This can also be | |
da0005b8 | 7 | controlled via the `blame.showRoot` config option. |
635f4a30 AR |
8 | |
9 | --show-stats:: | |
10 | Include additional statistics at the end of blame output. | |
11 | ||
e6d2b9f6 | 12 | -L <start>,<end>:: |
d349e0ee | 13 | -L :<funcname>:: |
a4514a46 PB |
14 | Annotate only the line range given by '<start>,<end>', |
15 | or by the function name regex '<funcname>'. | |
16 | May be specified multiple times. Overlapping ranges are allowed. | |
5bd9b79a | 17 | + |
fd5c74e7 PB |
18 | '<start>' and '<end>' are optional. `-L <start>` or `-L <start>,` spans from |
19 | '<start>' to end of file. `-L ,<end>` spans from start of file to '<end>'. | |
df83d5cf | 20 | + |
25ed3412 | 21 | include::line-range-format.txt[] |
635f4a30 AR |
22 | |
23 | -l:: | |
24 | Show long rev (Default: off). | |
25 | ||
26 | -t:: | |
27 | Show raw timestamp (Default: off). | |
28 | ||
29 | -S <revs-file>:: | |
b89510f0 | 30 | Use revisions from revs-file instead of calling linkgit:git-rev-list[1]. |
635f4a30 | 31 | |
e1d09701 | 32 | --reverse <rev>..<rev>:: |
b452cc16 MM |
33 | Walk history forward instead of backward. Instead of showing |
34 | the revision in which a line appeared, this shows the last | |
35 | revision in which a line has existed. This requires a range of | |
36 | revision like START..END where the path to blame exists in | |
e1d09701 JH |
37 | START. `git blame --reverse START` is taken as `git blame |
38 | --reverse START..HEAD` for convenience. | |
b452cc16 | 39 | |
11bc12ae RP |
40 | --first-parent:: |
41 | Follow only the first parent commit upon seeing a merge | |
42 | commit. This option can be used to determine when a line | |
43 | was introduced to a particular integration branch, rather | |
44 | than when it was introduced to the history overall. | |
45 | ||
3240240f SB |
46 | -p:: |
47 | --porcelain:: | |
635f4a30 AR |
48 | Show in a format designed for machine consumption. |
49 | ||
ed747dd5 JK |
50 | --line-porcelain:: |
51 | Show the porcelain format, but output commit information for | |
52 | each line, not just the first time a commit is referenced. | |
53 | Implies --porcelain. | |
54 | ||
635f4a30 AR |
55 | --incremental:: |
56 | Show the result incrementally in a format designed for | |
57 | machine consumption. | |
58 | ||
69cd8f63 AG |
59 | --encoding=<encoding>:: |
60 | Specifies the encoding used to output author names | |
61 | and commit summaries. Setting it to `none` makes blame | |
62 | output unconverted data. For more information see the | |
63 | discussion about encoding in the linkgit:git-log[1] | |
64 | manual page. | |
65 | ||
635f4a30 AR |
66 | --contents <file>:: |
67 | When <rev> is not specified, the command annotates the | |
68 | changes starting backwards from the working tree copy. | |
69 | This flag makes the command pretend as if the working | |
52727068 | 70 | tree copy has the contents of the named file (specify |
635f4a30 AR |
71 | `-` to make the command read from the standard input). |
72 | ||
31653c1a | 73 | --date <format>:: |
2df4e29c | 74 | Specifies the format used to output dates. If --date is not |
31653c1a EL |
75 | provided, the value of the blame.date config variable is |
76 | used. If the blame.date config variable is also not set, the | |
2df4e29c | 77 | iso format is used. For supported values, see the discussion |
31653c1a EL |
78 | of the --date option at linkgit:git-log[1]. |
79 | ||
aba37f49 ECA |
80 | --[no-]progress:: |
81 | Progress status is reported on the standard error stream | |
82 | by default when it is attached to a terminal. This flag | |
83 | enables progress reporting even if not attached to a | |
84 | terminal. Can't use `--progress` together with `--porcelain` | |
85 | or `--incremental`. | |
86 | ||
2b35a9f4 | 87 | -M[<num>]:: |
d8c416b2 JH |
88 | Detect moved or copied lines within a file. When a commit |
89 | moves or copies a block of lines (e.g. the original file | |
90 | has A and then B, and the commit changes it to B and then | |
91 | A), the traditional 'blame' algorithm notices only half of | |
92 | the movement and typically blames the lines that were moved | |
93 | up (i.e. B) to the parent and assigns blame to the lines that | |
94 | were moved down (i.e. A) to the child commit. With this | |
95 | option, both groups of lines are blamed on the parent by | |
96 | running extra passes of inspection. | |
3955d994 JH |
97 | + |
98 | <num> is optional but it is the lower bound on the number of | |
2de9b711 | 99 | alphanumeric characters that Git must detect as moving/copying |
3955d994 | 100 | within a file for it to associate those lines with the parent |
509de65f | 101 | commit. The default value is 20. |
635f4a30 | 102 | |
2b35a9f4 | 103 | -C[<num>]:: |
d8c416b2 | 104 | In addition to `-M`, detect lines moved or copied from other |
635f4a30 AR |
105 | files that were modified in the same commit. This is |
106 | useful when you reorganize your program and move code | |
107 | around across files. When this option is given twice, | |
88d50e78 RR |
108 | the command additionally looks for copies from other |
109 | files in the commit that creates the file. When this | |
110 | option is given three times, the command additionally | |
111 | looks for copies from other files in any commit. | |
3955d994 JH |
112 | + |
113 | <num> is optional but it is the lower bound on the number of | |
2de9b711 | 114 | alphanumeric characters that Git must detect as moving/copying |
3955d994 | 115 | between files for it to associate those lines with the parent |
509de65f BY |
116 | commit. And the default value is 40. If there are more than one |
117 | `-C` options given, the <num> argument of the last `-C` will | |
118 | take effect. | |
635f4a30 | 119 | |
ae3f36de BR |
120 | --ignore-rev <rev>:: |
121 | Ignore changes made by the revision when assigning blame, as if the | |
122 | change never happened. Lines that were changed or added by an ignored | |
123 | commit will be blamed on the previous commit that changed that line or | |
124 | nearby lines. This option may be specified multiple times to ignore | |
8934ac8c BR |
125 | more than one revision. If the `blame.markIgnoredLines` config option |
126 | is set, then lines that were changed by an ignored commit and attributed to | |
127 | another commit will be marked with a `?` in the blame output. If the | |
128 | `blame.markUnblamableLines` config option is set, then those lines touched | |
129 | by an ignored commit that we could not attribute to another revision are | |
130 | marked with a '*'. | |
ae3f36de BR |
131 | |
132 | --ignore-revs-file <file>:: | |
133 | Ignore revisions listed in `file`, which must be in the same format as an | |
134 | `fsck.skipList`. This option may be repeated, and these files will be | |
135 | processed after any files specified with the `blame.ignoreRevsFile` config | |
136 | option. An empty file name, `""`, will clear the list of revs from | |
137 | previously processed files. | |
138 | ||
3240240f | 139 | -h:: |
635f4a30 | 140 | Show help message. |