Not implemented Show blank SHA-1 for boundary commits. This can also be controlled via the `blame.blankboundary` config option.

Not implemented Use the same output mode as linkgit:git-annotate[1] (Default: off).

Not implemented In addition to `-M`, detect lines copied from other files that were modified in the same commit. This is useful when you reorganize your program and move code around across files. When this option is given twice, the command additionally looks for copies from all other files in the parent for the commit that creates the file. + alphanumeric characters that git must detect as moving between files for it to associate those lines with the parent commit.

Not implemented When is not specified, the command annotates the changes starting backwards from the working tree copy. This flag makes the command pretend as if the working tree copy has the contents of the named file (specify `-` to make the command read from the standard input).

Not implemented The value is one of the following alternatives: {relative,local,default,iso,rfc,short}. If --date is not provided, the value of the blame.date config variable is used. If the blame.date config variable is also not set, the iso format is used. For more information, See the discussion of the --date option at linkgit:git-log[1].

Not implemented Specifies the encoding used to output author names and commit summaries. Setting it to `none` makes blame output unconverted data. For more information see the discussion about encoding in the linkgit:git-log[1] manual page.

Not implemented Show help message.

Not implemented Show the result incrementally in a format designed for machine consumption.

Not implemented Show long rev (Default: off).

Not implemented Annotate only the given line range. and can take one of these forms:

Not implemented Detect moving lines in the file as well. When a commit moves a block of lines in a file (e.g. the original file has A and then B, and the commit changes it to B and then A), the traditional 'blame' algorithm typically blames the lines that were moved up (i.e. B) to the parent and assigns blame to the lines that were moved down (i.e. A) to the child commit. With this option, both groups of lines are blamed on the parent. + alphanumeric characters that git must detect as moving within a file for it to associate those lines with the parent commit.

Not implemented Show in a format designed for machine consumption.

Not implemented Walk history forward instead of backward. Instead of showing the revision in which a line appeared, this shows the last revision in which a line has existed. This requires a range of revision like START..END where the path to blame exists in START.

Not implemented Do not treat root commits as boundaries. This can also be controlled via the `blame.showroot` config option.

Not implemented Suppress the author name and timestamp from the output.

Not implemented Use revisions from revs-file instead of calling linkgit:git-rev-list[1].

Not implemented Include debugging information related to the movement of lines between files (see `-C`) and lines moved within a file (see `-M`). The first number listed is the score. This is the number of alphanumeric characters detected as having been moved between or within files. This must be above a certain threshold for 'git-blame' to consider those lines of code to have been moved.

Not implemented Show the filename in the original commit. By default the filename is shown if there is any line that came from a file with a different name, due to rename detection.

Not implemented Show the line number in the original commit (Default: off).

Not implemented Include additional statistics at the end of blame output.

Not implemented Show raw timestamp (Default: off).

Not implemented Ignore whitespace when comparing the parent's version and the child's to find where the lines came from.