]> git.ipfire.org Git - thirdparty/git.git/blame - Documentation/blame-options.txt
Merge branch 'for-junio' of git://source.winehq.org/~julliard/git/git
[thirdparty/git.git] / Documentation / blame-options.txt
CommitLineData
635f4a30
AR
1-b::
2 Show blank SHA-1 for boundary commits. This can also
3 be controlled via the `blame.blankboundary` config option.
4
5--root::
6 Do not treat root commits as boundaries. This can also be
7 controlled via the `blame.showroot` config option.
8
9--show-stats::
10 Include additional statistics at the end of blame output.
11
a44f88e2
AR
12-L <start>,<end>::
13 Annotate only the given line range. <start> and <end> can take
14 one of these forms:
15
16 - number
17+
18If <start> or <end> is a number, it specifies an
19absolute line number (lines count from 1).
20+
21
22- /regex/
23+
24This form will use the first line matching the given
25POSIX regex. If <end> is a regex, it will search
26starting at the line given by <start>.
27+
28
29- +offset or -offset
30+
31This is only valid for <end> and will specify a number
32of lines before or after the line given by <start>.
33+
635f4a30
AR
34
35-l::
36 Show long rev (Default: off).
37
38-t::
39 Show raw timestamp (Default: off).
40
41-S <revs-file>::
5162e697 42 Use revs from revs-file instead of calling linkgit:git-rev-list[1].
635f4a30 43
b452cc16
MM
44--reverse::
45 Walk history forward instead of backward. Instead of showing
46 the revision in which a line appeared, this shows the last
47 revision in which a line has existed. This requires a range of
48 revision like START..END where the path to blame exists in
49 START.
50
3240240f
SB
51-p::
52--porcelain::
635f4a30
AR
53 Show in a format designed for machine consumption.
54
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
73-M|<num>|::
74 Detect moving lines in the file as well. When a commit
75 moves a block of lines in a file (e.g. the original file
76 has A and then B, and the commit changes it to B and
77 then A), traditional 'blame' algorithm typically blames
78 the lines that were moved up (i.e. B) to the parent and
79 assigns blame to the lines that were moved down (i.e. A)
80 to the child commit. With this option, both groups of lines
81 are blamed on the parent.
3955d994
JH
82+
83<num> is optional but it is the lower bound on the number of
84alphanumeric characters that git must detect as moving
85within a file for it to associate those lines with the parent
86commit.
635f4a30
AR
87
88-C|<num>|::
89 In addition to `-M`, detect lines copied from other
90 files that were modified in the same commit. This is
91 useful when you reorganize your program and move code
92 around across files. When this option is given twice,
93 the command looks for copies from all other files in the
94 parent for the commit that creates the file in addition.
3955d994
JH
95+
96<num> is optional but it is the lower bound on the number of
97alphanumeric characters that git must detect as moving
98between files for it to associate those lines with the parent
99commit.
635f4a30 100
3240240f
SB
101-h::
102--help::
635f4a30 103 Show help message.