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 12-L <start>,<end>, -L :<regex>:: 13 Annotate only the given line range. <start> and <end> can take 14 one of these forms: 15 16include::line-range-format.txt[] 17 18-l:: 19 Show long rev (Default: off). 20 21-t:: 22 Show raw timestamp (Default: off). 23 24-S <revs-file>:: 25 Use revisions from revs-file instead of calling linkgit:git-rev-list[1]. 26 27--reverse:: 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 32 START. 33 34-p:: 35--porcelain:: 36 Show in a format designed for machine consumption. 37 38--line-porcelain:: 39 Show the porcelain format, but output commit information for 40 each line, not just the first time a commit is referenced. 41 Implies --porcelain. 42 43--incremental:: 44 Show the result incrementally in a format designed for 45 machine consumption. 46 47--encoding=<encoding>:: 48 Specifies the encoding used to output author names 49 and commit summaries. Setting it to `none` makes blame 50 output unconverted data. For more information see the 51 discussion about encoding in the linkgit:git-log[1] 52 manual page. 53 54--contents <file>:: 55 When <rev> is not specified, the command annotates the 56 changes starting backwards from the working tree copy. 57 This flag makes the command pretend as if the working 58 tree copy has the contents of the named file (specify 59 `-` to make the command read from the standard input). 60 61--date <format>:: 62 The value is one of the following alternatives: 63 {relative,local,default,iso,rfc,short}. If --date is not 64 provided, the value of the blame.date config variable is 65 used. If the blame.date config variable is also not set, the 66 iso format is used. For more information, See the discussion 67 of the --date option at linkgit:git-log[1]. 68 69-M|<num>|:: 70 Detect moved or copied lines within a file. When a commit 71 moves or copies a block of lines (e.g. the original file 72 has A and then B, and the commit changes it to B and then 73 A), the traditional 'blame' algorithm notices only half of 74 the movement and typically blames the lines that were moved 75 up (i.e. B) to the parent and assigns blame to the lines that 76 were moved down (i.e. A) to the child commit. With this 77 option, both groups of lines are blamed on the parent by 78 running extra passes of inspection. 79+ 80<num> is optional but it is the lower bound on the number of 81alphanumeric characters that Git must detect as moving/copying 82within a file for it to associate those lines with the parent 83commit. The default value is 20. 84 85-C|<num>|:: 86 In addition to `-M`, detect lines moved or copied from other 87 files that were modified in the same commit. This is 88 useful when you reorganize your program and move code 89 around across files. When this option is given twice, 90 the command additionally looks for copies from other 91 files in the commit that creates the file. When this 92 option is given three times, the command additionally 93 looks for copies from other files in any commit. 94+ 95<num> is optional but it is the lower bound on the number of 96alphanumeric characters that Git must detect as moving/copying 97between files for it to associate those lines with the parent 98commit. And the default value is 40. If there are more than one 99`-C` options given, the <num> argument of the last `-C` will 100take effect. 101 102-h:: 103 Show help message.