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 n,m:: 13 Annotate only the specified line range (lines count from 1). 14 15-l:: 16 Show long rev (Default: off). 17 18-t:: 19 Show raw timestamp (Default: off). 20 21-S <revs-file>:: 22 Use revs from revs-file instead of calling gitlink:git-rev-list[1]. 23 24-p, --porcelain:: 25 Show in a format designed for machine consumption. 26 27--incremental:: 28 Show the result incrementally in a format designed for 29 machine consumption. 30 31--contents <file>:: 32 When <rev> is not specified, the command annotates the 33 changes starting backwards from the working tree copy. 34 This flag makes the command pretend as if the working 35 tree copy has the contents of he named file (specify 36 `-` to make the command read from the standard input). 37 38-M|<num>|:: 39 Detect moving lines in the file as well. When a commit 40 moves a block of lines in a file (e.g. the original file 41 has A and then B, and the commit changes it to B and 42 then A), traditional 'blame' algorithm typically blames 43 the lines that were moved up (i.e. B) to the parent and 44 assigns blame to the lines that were moved down (i.e. A) 45 to the child commit. With this option, both groups of lines 46 are blamed on the parent. 47 48 <num> is optional but it is the lower bound on the number of 49 alphanumeric characters that git must detect as moving 50 within a file for it to associate those lines with the parent 51 commit. 52 53-C|<num>|:: 54 In addition to `-M`, detect lines copied from other 55 files that were modified in the same commit. This is 56 useful when you reorganize your program and move code 57 around across files. When this option is given twice, 58 the command looks for copies from all other files in the 59 parent for the commit that creates the file in addition. 60 61 <num> is optional but it is the lower bound on the number of 62 alphanumeric characters that git must detect as moving 63 between files for it to associate those lines with the parent 64 commit. 65 66-h, --help:: 67 Show help message.