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